-
-
Notifications
You must be signed in to change notification settings - Fork 25.8k
CI update lock files #23762
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
CI update lock files #23762
Conversation
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.
LGTM. I don't see any dramatic change apart of the uncertainty around setuptools
:)
Let's just wait for the CI to complete and then merge. |
There were some unexpected failures:
I also triggered full doc builds to make sure they pass. |
…ilds and doc builds
Let me try to see if I can reproduce the nogil crash locally to report upstream, independently of this PR. |
After the last CI runs:
Maybe good to merge? |
Yes ;) |
I could not reproduce the segfault on my local nogil setup on scikit-learn |
Merged! |
For information, I ran:
on my local |
I could not reproduce the segfault either locally ... let's wait and see if we this failure happens again in one of the nightly build |
Co-authored-by: Olivier Grisel <olivier.grisel@ensta.org>
Co-authored-by: Olivier Grisel <olivier.grisel@ensta.org>
Co-authored-by: Olivier Grisel <olivier.grisel@ensta.org>
I updated the lock files via the build_tools/update_environments_and_lock_files.py script.
I triggered all the nightly builds, the scipy-dev is not expected to pass since there are still failures in #23626.