-
Notifications
You must be signed in to change notification settings - Fork 912
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
Forward-merge branch-24.08 to branch-24.10 #16813
Forward-merge branch-24.08 to branch-24.10 #16813
Conversation
This is the changes that will be in the cudf-polars point release. --------- Co-authored-by: Thomas Li <[email protected]> Co-authored-by: David Wendt <[email protected]> Co-authored-by: brandon-b-miller <[email protected]> Co-authored-by: Vyas Ramasubramani <[email protected]> Co-authored-by: brandon-b-miller <[email protected]> Co-authored-by: Bradley Dice <[email protected]> Co-authored-by: Manas Singh <[email protected]> Co-authored-by: Manas Singh <[email protected]>
@@ -43,6 +47,9 @@ python -m pip install \ | |||
"$(echo ./dist/libcudf_${RAPIDS_PY_CUDA_SUFFIX}*.whl)" \ | |||
"$(echo ./dist/pylibcudf_${RAPIDS_PY_CUDA_SUFFIX}*.whl)" | |||
|
|||
rapids-logger "Pin to 1.7.0 Temporarily" |
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.
this can be removed now
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.
I would do those changes in a follow-up PR where we unpin and also change the xfail/xpass status of that one test we discussed.
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.
Thanks @bdice, I think the failures can be fixed by my suggestions, will try it out.
Oh, more merge conflicts! I'll resolve again. |
@mroeschke Can you please let this PR go through before merging any more pylibcudf changes? Or should we run CI locally on this and admin-merge it to avoid further delay? |
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.
I merged 24.10 and updated the workflow to point back to branch-24.10 (rather than python-3.12). From my side this looks good.
And the linting issues |
Update set of xfailing tests in polars test suite (we are passing two more tests...) |
# TAG=$(python -c 'import polars; print(f"py-{polars.__version__}")') | ||
TAG="py-1.7.0" |
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.
# TAG=$(python -c 'import polars; print(f"py-{polars.__version__}")') | |
TAG="py-1.7.0" | |
TAG=$(python -c 'import polars; print(f"py-{polars.__version__}")') |
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.
I think we're waiting to unpin this until a follow-up PR. This PR just needs to forward-merge the current state from 24.08 and we'll unpin/fix the associated problems on branch-24.10.
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.
Other than the comments about the temporary pinning, this is fine.
We need this in |
I probably won't need to admin-merge this, it looks like CI is running now (as my local CI run is running, too). But it'll still need ops to help non-squash-merge this, so I'm marking |
Manual forward merge from 24.08 to 24.10. This PR should not be squashed.