-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
upgrade spdlog to 1.8.5 and above #198
Conversation
rerun tests |
1 similar comment
rerun tests |
Blocked until |
rerun tests |
@rongou there are also conda conflicts in the |
rerun tests |
@mike-wendt conflicts are from |
rerun tests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved, but unable to merge
Is it ok to merge this now? |
@kkraus14 who should take on the PR testing to get this over the line? |
We should probably test similarly on cuDF and BlazingSQL at the minimum before we move forward. Will try to ping folks to see if they can replicate this testing. |
@kkraus14 can this be merged now? The RMM tests are passing rapidsai/rmm#658. |
Would still like to test cudf before merging. I'll open a PR bumping spdlog there for testing purposes. |
Opened PR here to test: rapidsai/cudf#8067 |
FYI -- Pinged BlazingSQL folks since they use spdlog where they're confirming that 1.8.5 is okay for them and then we'll merge. |
@kkraus14 Any update on this? |
PR is being thrown up to confirm this doesn't cause issues for them now. Hopefully should be straightforward. |
@kkraus14 have you heard back from them? |
Yes, apologies, this slipped through the cracks on my end. We should be good to go to proceed here. |
@kkraus14 can you approve this? Thanks! |
rerun tests |
1 similar comment
rerun tests |
Should be good to go, apologies. |
Fallout from rapidsai/rmm#658.