-
Notifications
You must be signed in to change notification settings - Fork 76
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
TST: Add RC testing workflow and update existing #1909
Conversation
Ugh... legit deprecation warning from pre-release... |
Codecov ReportBase: 91.96% // Head: 91.95% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #1909 +/- ##
==========================================
- Coverage 91.96% 91.95% -0.02%
==========================================
Files 140 140
Lines 15315 15326 +11
==========================================
+ Hits 14085 14093 +8
- Misses 1230 1233 +3
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 at Codecov. |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
Nevermind, nothing to do with voila.
|
6 out of 9 fixed in glue_astronomy 0.6.1; thanks for your contribution! |
There are still 4 failures in the dev job. FYI. |
Are the test_slice and test_region_spectral_spatial definitely connected to the units PR, too? I see the slice is somehow set from a wavelength with a unit, but don't have an idea how that would change its length. |
That I am not sure but astropy/specutils#999 isn't even merged yet so it can't be that. Maybe fix the two you know are tied to glue unit support first and see if the other two magically goes away. All we can do is the process of elimination. |
Already tested on my machine; it just fixes those two (and would obviate the need for glue-astronomy>=0.6.1). 🤷 |
OK, let's just worry about 2/4 first and defer the other two for later. Thanks! |
There is also a possibility that the other 2 would involve Jdaviz fixes to work with new unit support (e.g., calling internal API without unit no longer works) but I am just wildly guessing. A dev would have to investigate. |
sv = cubeviz.app.get_viewer(cubeviz._default_spectrum_viewer_reference_name)
sv.native_marks[0].x
# glue 1.6.1
array([ 3621.59598486, 3622.42998418, 3623.26417555, ..., 10353.80559518])
# glue-dev
array([ 0, 1, 2, 3, ..., 73]) Thus apparently in |
I think I've found where the remaining failures are coming from - more soon. |
I think glue-viz/glue#2358 fixes the remaining issues? |
We'll find out in 30 mins or so. I added a commit to test your PR branch on the dev job. |
Looks like I cannot test your branch here because your fork has no tags and glue-astronomy is pinning.
|
Should be ready to merge in a minute or so, tests are looking good! |
Dev job passed! |
and update existing
of 3 arcmin in the pre-release of astroquery 0.4.7.dev. Also make Catalog to not crash horribly when query fails. Update catalogs test results.
because upstream number of matches can change but that is not our problem.
but on Tuesdays
RC now passes, so I removed it from I wouldn't worry about the coverage. This is ready for review. FYI. |
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.
Do the changes in the catalogs plugin warrant a changelog entry?
Re: changelog entry I don't know what to write. This is upstream changes caused by astropy/astroquery#2477 but I wouldn't know enough server-side internals to write anything more useful than "I dunno, stuff changed". |
There are now discussions to revert this upstream at astropy/astroquery#2659 so I don't think we need a change log. Let's wait and see. Merging. |
Description
This pull request is to enable any maintainer to activate the workflow dispatch to test the next astropy release candidate instead of having to create a one-off throwaway PR.
Also minor updates to existing workflows.
Blocked by
Change log entry
CHANGES.rst
? If you want to avoid merge conflicts,list the proposed change log here for review and add to
CHANGES.rst
before merge. If no, maintainershould add a
no-changelog-entry-needed
label.Checklist for package maintainer(s)
This checklist is meant to remind the package maintainer(s) who will review this pull request of some common things to look for. This list is not exhaustive.
trivial
label.