-
Notifications
You must be signed in to change notification settings - Fork 285
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
Pin dask <2024.9 #6255
Pin dask <2024.9 #6255
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #6255 +/- ##
==========================================
+ Coverage 89.81% 89.83% +0.01%
==========================================
Files 88 88
Lines 23347 23347
Branches 4344 4344
==========================================
+ Hits 20970 20974 +4
+ Misses 1649 1646 -3
+ Partials 728 727 -1 ☔ View full report in Codecov by Sentry. |
We have an outstanding action to get the lockfiles working again, so that's going to get in your way: #6215 (comment) It's not a big thing, perhaps you and I could get that over the line this afternoon? |
…ask_slicing_bug * origin/pin_dask_slicing_bug: `date_microseconds` FUTURE flag (SciTools#6260) [pre-commit.ci] pre-commit autoupdate (SciTools#6259) Remove freepik.com link due to linkcheck breakage (SciTools#6261)
The doctest failure: I had a PR merged-and-released on Dask, which allowed me to remove this workaround: If we're using an older version of Dask then the above workaround needs to go back in. |
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.
- We should announce the pin and the reason in a What's New entry.
- Please can we have a new Iris issue that records the need to unpin in future.
Unpin dask when slicing bug is fixed #6264
⏱️ Performance Benchmark Report: b7a65b4Performance shifts
Full benchmark results
Generated by GHA run |
⏱️ Performance Benchmark Report: eeb1290Performance shifts
Full benchmark results
Generated by GHA run |
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 will need to return to the FF benchmark regression. Possibly this has come up because we're rolling back to an older Dask version? An issue will get raised overnight, which we can investigate in future.
⏱️ Performance Benchmark Report: 84cf32dPerformance shifts
Full benchmark results
Generated by GHA run |
⏱️ Performance Benchmark Report: 64abf74Performance shifts
Full benchmark results
Generated by GHA run |
* pin dask <2024.9 * update lockfiles * update for pypi * add whatsnew, fix tests * skip failing doctests
🚀 Pull Request
Description
Addresses #6251.
Note: it may be worth also adding a test for the bug encountered in #6251.This bug can be replicated without Iris, so this probably doesn't fall under our jurisdiction to test for.TODO: update the lockfiles.