-
Notifications
You must be signed in to change notification settings - Fork 296
[CI Bot] environment lockfiles auto-update #6597
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
base: main
Are you sure you want to change the base?
Conversation
⏱️ Performance Benchmark Report: 4068d5dPerformance shifts
Full benchmark results
Generated by GHA run |
⏱️ Performance Benchmark Report: 4068d5dPerformance shifts
Full benchmark results
Generated by GHA run |
⏱️ Performance Benchmark Report: 4068d5dPerformance shifts
Full benchmark results
Generated by GHA run |
b742c2c
to
afdf410
Compare
⏱️ Performance Benchmark Report: e98d344Performance shifts
Full benchmark results
Generated by GHA run |
afdf410
to
befcac5
Compare
⏱️ Performance Benchmark Report: fcfcc10Performance shifts
Full benchmark results
Generated by GHA run |
c0690ca
to
57ebd0e
Compare
⏱️ Performance Benchmark Report: e583ffePerformance shifts
Full benchmark results
Generated by GHA run |
⏱️ Performance Benchmark Report: a120396Performance shifts
Full benchmark results
Generated by GHA run |
57ebd0e
to
182dbdc
Compare
⏱️ Performance Benchmark Report: ff87d44Performance shifts
Full benchmark results
Generated by GHA run |
Those barb tests start by defining a magnitude as "scale" iris/lib/iris/tests/integration/plot/test_vector_plots.py Lines 104 to 106 in 345eea3
then u, v further get multiplied by 30 iris/lib/iris/tests/integration/plot/test_vector_plots.py Lines 195 to 197 in 345eea3
So our input magnitudes are basically
After all the various transformations, Matplotlib by default rounds magnitudes to the nearest 5 (see the rounding and barb_increments keywords in the docs). So it seems to me that our input magnitudes are ideally chosen to be sensitive to floating point errors. |
I have not checked, but the change might plausibly have been caused by something as simple as SciTools/cartopy#2509 |
Lockfiles updated to the latest resolvable environment.
If the CI tasks fail, create a new branch based on this PR and add the required fixes to that branch.