Repository navigation
CI: run full CI matrices on failures - #144
Merged
Merged
Conversation
* We've have CI failures plaguing us for months now (lanlgh-117, lanlgh-98, and others), and for GitHub Actions matrix jobs, when one entry in the matrix fails the rest of the jobs are then cancelled. This makes it hard for the reviewer to assess if new problems have been introduced to CI jobs that are not running. * This small patch allows all CI jobs in GHA matrices to run to completion, whether other matrix members fail or not, to make it easier for reviewers to assess what is going on. * This is pretty commonly used as one can see from other well-maintained repositories. For example, `git grep -E -i "fail-fast"` in the latest `main` branch of NumPy shows many uses of `fail-fast: false`.
Collaborator
Author
|
This is clearly correct and important for reviewers. I'd prefer to have others review these, but I'll go ahead and self-merge since this is blocking assessment of other PRs... |
tylerjereddy
added a commit
to tylerjereddy/GFDL
that referenced
this pull request
Oct 30, 2026
* Fixes lanlgh-122. CPython `3.15` has been out for a few weeks now--see: https://www.python.org/downloads/release/python-3150/ * I checked our latest `main` branch against Python `3.15.2` locally on x86_64 Linux, and the tests passed apart from the known failures of lanlgh-145 and lanlgh-117. So, here I'm proposing to activate CI testing for the latest stable release of Python. * It might make sense to have lanlgh-144 merge first, because we may not be able to see the `3.15` jobs running here to assess them otherwise. * I've also updated our trove classifier to reflect `3.15` support in the next stable release we do.
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.
We've have CI failures plaguing us for months now (TST, CI:
test_partial_fitis failing in Linux CI (with NumPy2.5.0) #117, TST, CI:test_regression_bostonsometimes failing in CI #98, and others), and for GitHub Actions matrix jobs, when one entry in the matrix fails the rest of the jobs are then cancelled. This makes it hard for the reviewer to assess if new problems have been introduced to CI jobs that are not running.This small patch allows all CI jobs in GHA matrices to run to completion, whether other matrix members fail or not, to make it easier for reviewers to assess what is going on.
This is pretty commonly used as one can see from other well-maintained repositories. For example,
git grep -E -i "fail-fast"on the latestmainbranch of NumPy shows many uses offail-fast: false.AI usage disclosure: I asked Opus
5.5to adjust all GHA config files with matrix usage accordingly.