chore(ci): Split pre-release tests into cron job, open issues on failure#3746
Merged
chore(ci): Split pre-release tests into cron job, open issues on failure#3746
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #3746 +/- ##
=======================================
Coverage 72.88% 72.88%
=======================================
Files 1279 1279
Lines 59351 59351
=======================================
Hits 43256 43256
Misses 16095 16095 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In #3745, the pre-release tests are failing, causing other the PR to fail. This is generally not desirable, as these are rarely the fault of contributor PRs. This pulls the prerelease tests into their own workflow, run on a schedule rather than PR. The
ci/prereleasebranch can be used to debug and fix issues.@Remi-Gau helped me set this up in nibabel.
Incidentally, also split the install and test tox stages. Sometimes install can fail or take a long time due to infrastructure issues, and it's nice to separate that from test failures at a glance.