Add CI rule that triggers once a week with the full test suite. #485
Conversation
This file contains 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
Remove Fortran flag that doesn't seem to have any effect. Slightly reword group title when re-running failed tests.
Currently, this is basically a copy of the build rules that trigger on pull requests or pushes. The only difference is that the trigger is on a weekly schedule and the full set of tests are run. Mid-term, more tests could be run for different configurations on PRs or pushes (e.g., build tests with bundled or external dependencies, with some enabled or disabled features, with different compilers, on different platforms, ...) while the full test suite is only run with one or a different subset of configurations. That will be easier if we start with two sets of (currently basically identical) rules and let them spread in different directions from here without having to care about the other rules.
|
Modifying the schedule to run more or less often should be quite straight-forward. Please, let me know if you prefer to do that as part of this PR. |
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.
Currently, this is basically a copy of the build rules that trigger on pull requests or pushes. The only difference is that the trigger is on a weekly schedule and the full set of tests are run.
Mid-term, more tests could be run for different configurations on PRs or pushes (e.g., build tests with bundled or external dependencies, with some enabled or disabled features, with different compilers, on different platforms, ...) while the full test suite is only run with one or a different subset of configurations.
That will be easier if we start with two sets of (currently basically identical) rules and let them spread in different directions from here without having to care about the other rules.
I don't know what "activating the "elmerice" capabilities/tests" means. So, I didn't touch anything in the existing configuration.
Could you please let me know if something should be changed?