Schedule running the extra system tests cases#866
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
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.
While most tests are included in the
releasetest suite, some take much longer to run, for which reason they are in theextratest suite. Most of these are also not adding much value compared to other cases, since they would mostly be affected by changes in their configuration. Still, we need to test them.This PR adds a short workflow that triggers these extra test cases once per week. The day is arbitrary, but having a test fail in the middle of the week would be nicer than in the beginning/end of the week.
It also adjusts the execution of the
releasetest suite to start 2h earlier, as the job always seems to finally start in the late morning. I understand that there is a lot of competition on triggering scheduled events on GHA, even though we are using our own runner.This leads to:
releasetest suiteextratest suitereleaseis not done by the timeextrastarts, it will just wait.Testing the
extratest suite in https://github.com/precice/tutorials/actions/runs/28859073065/job/85592833771