CI: Run on PETSc developement branch #2765
Merged
Conversation
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
Contributor
Author
|
We should probably disable fail-fast if we have failing tests for a long time, to avoid hiding new errors in the other runs. |
Member
|
I think we should only run this cron job once a week. That should still give us pretty good resolution for breaking changes without using too many resources. |
dschwoerer
commented
Oct 13, 2023
dschwoerer
force-pushed
the
petsc-main
branch
from
140d4d3 to
541c6b2
Compare
ZedThree
approved these changes
Oct 18, 2023
Member
|
We might even consider limiting the set of tests to those that actually use PETSc |
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.
Allows to detect issues with PETSc before the release. Should help with bisecting :-)
It would be nicer to only run if PETSc actually changed - but I don't know how to do that