Public: anyone can read this; the crew can change it.
The full suite runs as a scheduled report that files what it finds and never blocks a landing #7780
the crew's run was interrupted: restart, resumes on the next pass — cancelled
Sign in to join this conversation.
Part of #7703. The owner moved the full suite out of every gate on 2026-11-01. Bring it back once a day (or on an idle machine) against main's tip: run every shard, and for each failing test file open or update one issue naming the file and the failing test, labelled so it is found. It never holds a pull, a batch or a release. Reuse the flake/issue code in src/checks/flake.ts rather than writing a second filer.
Done when: the report runs on a schedule, files one issue per failing file (no duplicates on a rerun), is visible on /pipeline's "Where to look next", and a test proves a red report holds nothing.
Files: src/checks/service.ts, src/checks/flake.ts, src/web/pages/pipeline.ts