Nightly parity audit on the Mac mini, with an issue per regressed harness

nightly.yml runs every harness from scratch on main at 03:00 Paris time on the Mac mini's runner, after
preparing the resources again if the preparer changed. tools/ci/parity_issues.py compares the results with
the previous audit: a harness that passed and now fails gets one issue labelled parity-regression (an open
one is commented on), and an issue closes when its harness passes again. The bugs session picks them up.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Ludovic Marie
2026-10-14 18:54:17 +02:00
parent 98ca844f07
commit beac11eaa5
4 changed files with 233 additions and 0 deletions
+16
View File
@@ -211,3 +211,19 @@ see the previous one as the newest; launchers that already updated keep running.
With several game releases a day, the newest launcher release soon falls out of the newest 100 releases the
launcher and the website read: both then look the newest `launcher-v` tags up one by one
(`git/matching-refs/tags/launcher-v`, then `releases/tags/<tag>`).
## Nightly audit
`.github/workflows/nightly.yml` runs every harness from scratch (`tools/parity.py --all`) on main at 03:00 Paris
time, on the Mac mini's runner, after preparing the resources again if the preparer or its exporters changed.
`tools/ci/parity_issues.py` then compares the results with the previous audit
(`.local/parity-runner/audit.json` in the runner's checkout):
- a harness that passed last night and fails now gets an issue labelled `parity-regression`, titled
`Parity regression: <harness>`, with the commit, the run and the end of its log (one issue per harness: an open
one gets a comment instead);
- a harness with an open issue that passes again gets its issue closed.
The bugs session picks the issues up. The audit's logs are the run's `nightly-parity-logs` artifact; harnesses
listed `linux_only` are skipped there (see above). By hand: `gh workflow run "nightly audit"` (add
`-f dry_run=true` to leave issues alone).