-
Notifications
You must be signed in to change notification settings - Fork 87
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
Update upstream-dev testing infrastructure #654
Comments
Sounds great. Current state of rioxarray latest testing: rioxarray/.github/workflows/tests.yaml Lines 165 to 212 in d492a2a
|
The issue with latest was that the build failed often due to installation issues or other noise that unfortunately made it less useful. It just barely stabilized enough to get useful testing information. |
That's really cool! @dcherian mind if I grab that for |
@Zeitsperre go for it! The cf-xarray version also supports adding a |
### What kind of change does this PR introduce? * Splits the existing upstream testing stage into its own workflow * This workflow uses xarray-developed actions for opening issues when this workflow fails * Is triggered when a PR is merged to master or every day at midnight. * Can be triggered via cron job or manually (using `workflow_dispatch`) * Unites the CI workflows for PyPI/`tox`-based jobs into one action with a strategy matrix ### Does this PR introduce a breaking change? No. ### Other information: See: corteva/rioxarray#654
Xarray has a fancy new nightly upstream testing workflow.
It runs nightly and opens nice issues with test logs (example). It'd be nice to copy that over here so things like #652 can be caught more proactively.
The text was updated successfully, but these errors were encountered: