Repository navigation
CI: allow-fail units need an owner and an expiry (ultraplan Phase 2.3) #416
Description
Tracking issue for ultraplan Phase 2.3 (docs/planning/ULTRAPLAN-2026-10-09.adoc).
Every continue-on-error: true in .github/workflows/ now needs an owner and an expiry date on the same line. A checker (scripts/ci/check-allow-fail-expiry.py, run by the workflow linter) fails CI when a marker is missing, malformed, or past its date.
Marker format: continue-on-error: true # allow-fail: issue=#<n> expires=YYYY-MM-DD
Default expiry for this batch: 2026-11-30. At expiry, each unit is either made blocking, re-justified with a new date, or removed. The checker does not decide which. A human does.
Inventory at 2026-10-09 (14 units):
| File | Unit | Note |
|---|---|---|
| boj-build.yml | step trigger-boj |
BoJ trigger |
| chapel-ci.yml | job rust-chapel-feature |
depends on zig-ffi (#133) |
| chapel-ci.yml | job rust-chapel-real |
real Chapel link, see #408 |
| container-ci.yml | job tier3-container |
|
| live-provers.yml | job tier1-guix-reproducibility |
|
| live-provers.yml | step tier2 provision |
best-effort install |
| live-provers.yml | job tier3 |
|
| live-provers.yml | step tier3 provision |
best-effort install |
| live-provers.yml | job tier4 |
|
| live-provers.yml | job tier4-gpu |
CUDA/OpenCL required |
| live-provers.yml | step tier4-gpu provision |
|
| live-provers.yml | step tier4-gpu version check |
|
| static-analysis-gate.yml | step hypatia-scan Elixir setup |
see #314 |
| static-analysis-gate.yml | step hypatia-scan clone and build |
see #314 |
Acceptance: the checker passes on main, and no unit lacks a marker.
Activity
ci: CI hygiene — allow-fail expiry, dead playground workflows, rulese…
CI hygiene: allow-fail expiry, dead playground workflows, ruleset sna…