-
Notifications
You must be signed in to change notification settings - Fork 54
Add Python 3.13, and update shared-workflows. #150
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
Conversation
|
@gmarkall It'd be great to have your eyes on some of these failures. Are any of them expected? |
|
@bdice Thanks for the PR! These are not expected, but they all seem to have a common cause - I'll take a look. |
|
We will need rapidsai/pynvjitlink#131 and a pynvjitlink release to unblock Python 3.13 tests. That PR is ready and just needs a final review, so I think a new release might be able to ship today. If the other segfault issues on this PR are worked out before that release, we can temporarily roll those jobs back to Python 3.12. |
|
I fixed up the CI matrix and made sure we have supported image tags across the matrix. I think there are only two root causes of the CI failures to address. The conda CUDA 11.4 job is showing: The CUDA 12.8 / Python 3.13 jobs (for conda and wheels and pynvjitlink) are showing a segfault in |
|
The failing tests are net-new coverage in the test suite. I would like to propose breaking this down, to make solving the issues easier and more atomic.
|
|
Update: the segfault still occurs with Python 3.12. Maybe the segfault wasn't due to Python 3.13, perhaps it was something with the OS (ubuntu24.04) or CUDA version (12.8.0). I will try another combination of matrix options to isolate what is causing this. |
|
pynvjitlink 0.5.1 is released, with Python 3.13 support. There is one test failure remaining on the conda pynvjitlink job: I am trying to rerun the job but I suspect this will need further investigation. |
|
I have narrowed the failures a bit.
Python 3.13 and Ubuntu 24.04 do not appear to have any issues, so my earlier commits were a bit misleading. I recommend we merge this as-is, so that we are more aligned with the (wider) RAPIDS build/test matrix and have the actions updates that we need in this repo. Then we can work through the failures in follow-up PRs. |
brandon-b-miller
left a comment
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 , just to confirm my understanding, we're currently passing by not spawning jobs in the buggy configurations, right? If so, can we just make sure we have an issue documenting what those configurations are and what errors they produce?
|
@brandon-b-miller Yes -- that's exactly my plan. I have filed issues based on these findings. I will open PRs that demonstrate each failure separately after merging this. |
* Drop Python 3.9, add Python 3.13, and update shared-workflows. * Add back Python 3.9. * Fix requires-python. * Correct test matrix. * Use supported CUDA 12.2.2 Ubuntu version. * Fix lack of CUDA 11.4 images for citestwheel. * Fix pynvjitlink support matrix. * Temporarily disable Python 3.13 and CUDA 11.4 tests. * Try CUDA 12.5 and Ubuntu 24.04 separately. * Skip CUDA 12.8, but test Python 3.13 and Ubuntu 24.04. * Test older Ubuntu version. * Try with Python 3.11. * Use l4 GPU. * Try newer Python and OS again.
This PR adds Python 3.13 to CI, and updates the workflows to align with updates from RAPIDS'
shared-workflowsupstream.