-
Notifications
You must be signed in to change notification settings - Fork 167
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
JP-3664: Testing changes for numpy 2.0 compatibility #8718
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #8718 +/- ##
=======================================
Coverage 63.68% 63.68%
=======================================
Files 375 375
Lines 38689 38691 +2
=======================================
+ Hits 24638 24640 +2
Misses 14051 14051 ☔ View full report in Codecov by Sentry. |
61f372c
to
bcba8a3
Compare
f90c0c6
to
37bab62
Compare
#8812 fixed most of the coron unit tests with numpy 2, but there's still one check that's barely out of spec on the Linux tests. I think changing these lines to atol=1e-4, rtol=1e-5 should work: jwst/jwst/coron/tests/test_coron.py Lines 144 to 145 in 217d660
|
7784bb9
to
3b59528
Compare
Resolves JP-3664
Closes #8580
This draft exists to remove jwst's upper pin on numpy, as well as provides a spot to test changes to coron3 unit tests that appear to be incompatible with np2.0.
Checklist for PR authors (skip items if you don't have permissions or they are not applicable)
CHANGES.rst
within the relevant release sectionHow to run regression tests on a PR