Make systemtest runs portable and re-runnable from CI artifacts#724
Make systemtest runs portable and re-runnable from CI artifacts#724PranjalManhgaye wants to merge 2 commits into
Conversation
There was a problem hiding this comment.
Pull request overview
This PR aims to make system test run directories portable and re-runnable from downloaded CI artifacts by switching generated Docker Compose files to relative paths, adding a local rerun helper script, updating default tutorial refs, and documenting the workflow.
Changes:
- Generate Docker Compose files using relative paths (intended to avoid CI-runner-specific absolute paths).
- Create a
rerun_systemtest.shhelper script inside each system test run directory. - Update
TUTORIALS_REFdefaults todevelopand document how to rerun tests from CI artifacts.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
| tools/tests/systemtests/Systemtest.py | Switches compose generation to relative paths and adds a rerun helper script. |
| tools/tests/components.yaml | Updates default TUTORIALS_REF from master to develop. |
| tools/tests/README.md | Adds documentation for rerunning system tests from CI artifacts. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
@MakisH i have resolved the suggested changes by copilot , review it once , thanks |
9e05394 to
558edba
Compare
Use relative Docker Compose paths, generate rerun_systemtest.sh in each run folder, and document replay from system_tests_run_*_full artifacts. Closes precice#387.
558edba to
ddd0eac
Compare
MakisH
left a comment
There was a problem hiding this comment.
This PR could also be interesting to integrate. Please update from develop and see some more comments.
Integrate current develop for PR precice#724 and address review feedback: standalone tools/tests/rerun_systemtest.sh copied into each run directory, relative Docker Compose paths for portable CI artifact replay. Closes precice#387.
|
@MakisH thanks for a review and i merged develop and fixed the standalone rerun_systemtest.sh thing and it's ready for another look,thanks,, |
Summary
When a system test fails in CI, we often download the
system_tests_run_*_fullartifact to debug locally (#387). The old compose files used absolute runner paths, so replay on another machine usually broke unless you fixed paths by hand.This PR makes run folders portable: relative paths, a
rerun_systemtest.shhelper,TUTORIALS_REFdefaultdevelop, and short README notes on replay.Closes #387.
What changed
Systemtest.py:run_directory→"..", dockerfiles →../tools/tests/dockerfiles/<PLATFORM>, plusrerun_systemtest.sh(same commands as the Python runner). ( only + 66 -6 )README.md: how to unzip a full artifact and re-run.changelog-entries/724.mdAfter unzip, layout is
runs/tools/(shared) + one folder per test; you work inside the test folder.Testing
I tested locally with quickstart (build, run, fieldcompare),
rerun_systemtest.sh(original + copied tree), and one CI artifact replay. I did not run the fulltests.yamlmatrix here — happy if you trigger system tests on CI.The #387 example artifact is expired; new runs after merge should work without path patching.