You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: tools/tests/README.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,6 +54,12 @@ To be able to fill in the right case tuple into the `tests.yaml`, you can use th
54
54
55
55
## Running the system tests on GitHub Actions
56
56
57
+
Pull-request system tests run as a GitHub Actions matrix over `release_test_shard_1` and
58
+
`release_test_shard_2` (together they cover the same cases as `release_test`). When a shard
59
+
fails, re-run only the failed matrix job. With multiple `precice-tests-vm` runners, shards
60
+
may execute concurrently; overlapping Docker image builds are possible and acceptable unless
61
+
CI reports failures.
62
+
57
63
Go to Actions > [Run Testsuite (manual)](https://github.com/precice/tutorials/actions/workflows/run_testsuite_manual.yml) to see this workflow.
58
64
59
65
After bringing these changes to `master`, the manual triggering option should be visible on the top right. Until that happens, we can only trigger this workflow manually from the [GitHub CLI](https://github.blog/changelog/2021-04-15-github-cli-1-9-enables-you-to-work-with-github-actions-from-your-terminal/):
0 commit comments