Skip to content
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

Merged
merged 4 commits into from
Feb 8, 2023

Conversation

pllim
Copy link
Contributor

@pllim pllim commented Dec 8, 2022

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

  • Is a change log needed? If yes, is it added to 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, maintainer
    should 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.

  • Are two approvals required? Branch protection rule does not check for the second approval. If a second approval is not necessary, please apply the trivial label.
  • Do the proposed changes actually accomplish desired goals? Also manually run the affected example notebooks, if necessary.
  • Do the proposed changes follow the STScI Style Guides?
  • Are tests added/updated as required? If so, do they follow the STScI Style Guides?
  • Are docs added/updated as required? If so, do they follow the STScI Style Guides?
  • Did the CI pass? If not, are the failures related?
  • Is a milestone set? Set this to bugfix milestone if this is a bug fix and needs to be released ASAP; otherwise, set this to the next major release milestone.
  • After merge, any internal documentations need updating (e.g., JIRA, Innerspace)? 🐱

@pllim pllim added trivial Only needs one approval instead of two no-changelog-entry-needed changelog bot directive labels Dec 8, 2022
@pllim pllim added this to the 3.2 milestone Dec 8, 2022
@pllim
Copy link
Contributor Author

pllim commented Dec 8, 2022

Ugh... legit deprecation warning from pre-release...

@codecov
Copy link

codecov bot commented Dec 8, 2022

Codecov Report

Base: 91.96% // Head: 91.95% // Decreases project coverage by -0.02% ⚠️

Coverage data is based on head (82da9df) compared to base (3fc9a92).
Patch coverage: 78.57% of modified lines in pull request are covered.

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     
Impacted Files Coverage Δ
jdaviz/configs/imviz/plugins/catalogs/catalogs.py 90.22% <72.72%> (-1.65%) ⬇️
jdaviz/configs/imviz/tests/test_catalogs.py 100.00% <100.00%> (ø)

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.
📢 Do you have feedback about the report comment? Let us know in this issue.

@pllim

This comment was marked as resolved.

@rosteen rosteen modified the milestones: 3.2, 3.3 Jan 4, 2023
@pllim

This comment was marked as resolved.

@pllim
Copy link
Contributor Author

pllim commented Jan 31, 2023

Nevermind, nothing to do with voila.

@dhomeier
Copy link
Collaborator

6 out of 9 fixed in glue_astronomy 0.6.1; thanks for your contribution!

@pllim
Copy link
Contributor Author

pllim commented Jan 31, 2023

There are still 4 failures in the dev job. FYI.

@dhomeier
Copy link
Collaborator

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.

@pllim
Copy link
Contributor Author

pllim commented Feb 1, 2023

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.

@dhomeier
Copy link
Collaborator

dhomeier commented Feb 1, 2023

Already tested on my machine; it just fixes those two (and would obviate the need for glue-astronomy>=0.6.1). 🤷

@pllim
Copy link
Contributor Author

pllim commented Feb 1, 2023

OK, let's just worry about 2/4 first and defer the other two for later. Thanks!

@pllim
Copy link
Contributor Author

pllim commented Feb 1, 2023

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.

@dhomeier
Copy link
Collaborator

dhomeier commented Feb 1, 2023

test_slice definitely indicates a regression. With the glue update, the spectrum_viewer.native_marks the wavelength is selected in are apparently just a list of indices rather than the values in Angstrom. In the CubevizExample notebook:

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 Slice the last native_mark is selected.
The spectrum-viewer window in the notebook looks correspondingly broken.

@astrofrog
Copy link
Collaborator

I think I've found where the remaining failures are coming from - more soon.

@astrofrog
Copy link
Collaborator

I think glue-viz/glue#2358 fixes the remaining issues?

@pllim
Copy link
Contributor Author

pllim commented Feb 2, 2023

We'll find out in 30 mins or so. I added a commit to test your PR branch on the dev job.

@pllim
Copy link
Contributor Author

pllim commented Feb 2, 2023

Looks like I cannot test your branch here because your fork has no tags and glue-astronomy is pinning.

The conflict is caused by:
    The user requested glue-core 0.1.dev6554+gd212e9b (from git+https://github.com/astrofrog/glue.git@fix-unit-update)
    glue-astronomy 0.6.2.dev3+g71ded78 depends on glue-core>=1.6.1

@dhomeier
Copy link
Collaborator

dhomeier commented Feb 2, 2023

Should be ready to merge in a minute or so, tests are looking good!

@pllim
Copy link
Contributor Author

pllim commented Feb 2, 2023

Dev job passed!

pllim added 2 commits February 7, 2023 11:20
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.
@pllim pllim marked this pull request as ready for review February 7, 2023 17:39
but on Tuesdays
@pllim
Copy link
Contributor Author

pllim commented Feb 7, 2023

RC now passes, so I removed it from pull_request trigger. Going forward, it can be manually triggered by a maintainer but it also runs weekly after merge.

I wouldn't worry about the coverage.

This is ready for review. FYI.

Copy link
Member

@kecnry kecnry left a 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?

@pllim
Copy link
Contributor Author

pllim commented Feb 7, 2023

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".

@pllim
Copy link
Contributor Author

pllim commented Feb 8, 2023

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.

@pllim pllim merged commit 95c34c2 into spacetelescope:main Feb 8, 2023
@pllim pllim deleted the rc-testing branch February 8, 2023 22:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-changelog-entry-needed changelog bot directive testing trivial Only needs one approval instead of two
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants