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: docs/release_artifacts.md
+46Lines changed: 46 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,6 +58,52 @@ python tools\release_audit.py
58
58
59
59
The GitHub Release workflow runs the packaged simulator audit in both the Linux and Win64 jobs before uploading artifacts. Those CI audits use `--skip-visualizer` because hosted runners are headless.
60
60
61
+
## Reviewer quick start
62
+
63
+
The released binaries are command-line tools. Running them with no arguments prints usage; reviewers should use the exact commands below.
- The Linux bundle uses `run-testrig.sh` and `run-visualizer.sh` as the supported entry points because they set `LD_LIBRARY_PATH` for the bundled runtime library directory.
104
+
- The Win64 bundle does not include `run-*.sh` wrappers. On Windows, launch the `.exe` files directly; on Linux, launch them with `wine`.
105
+
- The visualizer always needs at least one JSON input path, and the shipped bundle is `visualization/scenarios.json`.
106
+
61
107
## Local artifact testing
62
108
63
109
Local artifact testing exercises the packaged bundles, not just the build tree:
0 commit comments