-
Notifications
You must be signed in to change notification settings - Fork 65
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
Expand test coverage #854
Expand test coverage #854
Conversation
Immediate test failures:
No idea what this means |
Actually the |
https://github.com/radio-astro-tools/spectral-cube/actions/runs/4374807279/jobs/7654700456#step:5:1516 we have real failures in some tests because of unimplemented floor_divide? I hope this just means we need to bump version numbers |
Codecov ReportPatch coverage:
📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more Additional details and impacted files@@ Coverage Diff @@
## master #854 +/- ##
==========================================
+ Coverage 77.36% 79.88% +2.51%
==========================================
Files 24 24
Lines 6027 6035 +8
==========================================
+ Hits 4663 4821 +158
+ Misses 1364 1214 -150
... and 5 files with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
There's at least one genuine bug here introduced by astropy upstream. This test: |
I don't see any sign of this breaking change in astropy's changelog. The only way I can think to track it down is with bisection, which I'm really bad at and can't do on my personal computer. |
Maybe this is our breaking change? astropy/astropy@c6ff27d |
No, that seems like it's not the problem; the default is to pass on info except for a few cases that don't apply to these tests. |
I had to do some test refactoring to get tests to run locally at all. |
right, so, it looks like noviz works, but 'all' doesn't. |
OK, dev passes on its own, so it's not dev. It's some interaction between the viz stuff and the dev stuff, but I'm not convinced the viz stuff works at all. Split up the tests further. |
So getting rid of the 'all' mode has solved my local woes - I can now test everything in a grid locally. This seems also to have "fixed" tests remotely. But I think this makes no sense, so I'm worried I've done something that I don't understand. |
Dev and viz independently cause failures. The dev failures originate somewhere in quantity, but there's no difference in astropy quantity between 5.2.1 and 5.3.dev, so I'm stuck. |
I can't test dev locally because:
I'm at a loss with this; I've googled and found similar issues, but no fixes - the issues just end with 'oh ok we solved it' |
the viz tests are amusing:
I think this is an indication that the tests crash completely as soon as |
https://github.com/radio-astro-tools/spectral-cube/actions/runs/4384619998/jobs/7676312293#step:5:1534 is pointing to an incorrect error being raised:
|
I finally tracked down one error: astropy/astropy#14514. |
ok last (?) open issue:
|
All of the relevant tests have been stuck yellow for hours? Did I overuse our minutes or something? |
no... I tihnk I introduced an infinite loop 🤦 |
Got dev to go green, finally. Have a yt error:
|
Note that this depends on astropy/reproject#349 |
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.
@keflavich Looks good. Just some questions on the LDO creation without a WCS and whether that should be allowed or not.
expand test coverage fix test failure for dask trivial whitespace change? try to emulate astropy/astroquery#2626 that last one seems to maybe have broken CI? undoing the CI changes try putting things on one line ? try changing ubuntu-latest to linux based on the versions-manifest, which doesn't mention ubuntu at all try changing 3.10 -> '3.10' instead of the linux change shorten job names so we can see the whole name in the sidebar of gh-actions add a mask setter to solve problem where numpy masked arrays are trying to set the mask attribute but being blocked from doing so drop openfiles b/c it's deprecated (not sure what we're supposed to replace it with yet) make some of the failing tests more extensive and explicit
…ming from (pdb revealed that code that succeeded on the previous line is the direct source of this failure) fix mistake add a new test for "all" add all-dev and remove -openfiles from windoze move dev dependenc installs from tox to setup.cfg whitespace and naming expand test coverage yet again: try dev w/o novis/all separate out 'viz' from 'noviz' fix a typo.... add extras that were all missing into tox.ini make sure basic tests use latest numpy rearrange and make tests more granular still drop 3.7 from grid b/c astropy 5.2.1 doesn't support it see if pvextractor can be included in the "good" viz hack around astropy 14514 hack needs to be hackier b/c _new_view didn't always have finalize= option try to run tests w/dev branch fix syntax fix install url fix name again? try to fix last exception allow for three types of error? this might not be the right approach fix test again remove mask setter - I'm not sure it was actually needed, I think that might have been a side-effect error caused by something else? Pushing this to run tests to check; may neeed to partially revert this if tests fail set ndim fix the naxis defn restore the mask setter, it _is_ needed reproject high_level_wcs fix merged; revert to master in tests fix names of # of dims
ah crud. Everything is not fine. |
…ke tests go green again
OK so something changed in astropy-dev in the last 4 days that broke this. I'll bisect this time. |
Broken by astropy/astropy#14508. Can't stay ahead of astropy! |
In the last commit, I was trying to replicate this line: what did I get wrong? |
… go green for <24h b/c the breaking change is <8h old, but the intent is to make builds faster change order of commands oh, I just had stupidly pasted in setup.cfg too
And make sure tests are still passing in prep for a new release (0.6.1)