-
-
Notifications
You must be signed in to change notification settings - Fork 25.9k
🔒 🤖 CI Update lock files for main CI build(s) 🔒 🤖 #29276
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 for main CI build(s) 🔒 🤖 #29276
Conversation
The CI issue comes from pyamg uses The short-term fix is to ignore the warning similarly to pyamg warnings which are already ignored. |
+1 |
99b3de3
to
180e9fa
Compare
pyamg 5.2 has been released without the DeprecationWarning due to Numpy 2, so I guess the best thing to do is to wait until next Monday and see what happens on the next bot schedule run. See pyamg/pyamg#406. |
180e9fa
to
130ce2e
Compare
27 failures from one Azure build log. Here is a quick summary looking at the different errors. doctests differences likely due to scipy 1.13 -> 1.14?Probably a work-around is to skip doctests in some settings, there is already some logic to do this.
array API issueslikely due to array-api-strict 1.1 -> 2.0 update?
Cryptic CircleCI failure (segmentation fault?)
|
Scipy bumped into array-api-strict 2 issues: scipy/scipy#21074, some were fixed in 2.0.1 released yesterday but locally I still get some issue about searchsorted and
|
I have opened #29385 to fix the doctests to be compatible for scipy>=1.14. |
This is taken over by #29388 since this requires quite a few changes. I let this open otherwise the bot will open a separate PR on Monday and we want to have all the info in the same PR. |
76940df
to
8efbaeb
Compare
Update lock files.
Note
If the CI tasks fail, create a new branch based on this PR and add the required fixes to that branch.