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
{{ message }}
Repository navigation
Commit ba406d0
Browse filesBrowse the repository at this point in the historyBrowse files
chore(release): v1.9.0 — changelog, version bump, and CI-parity guard
CHANGELOG carries the release; build.zig.zon moves to 1.9.0.
Rides with it, found by checking CI before tagging: budget_thread_ownership.sh
used a bare `timeout` and python3 clock, and the CI macOS runner ships neither
GNU timeout nor gtimeout — exit 127, the step failed at 0s. Locally green, red
on push, the SECOND time this exact class has bitten (check_doc_coverage.sh,
2026-08-04), both times with the in-repo `run_bounded` fix sitting unused.
So the fix is mechanical this time: scripts/check_portable_timeout.sh fails
the gate (smoke included) on any bare `timeout` in a gate-reachable script —
every test/e2e/*.sh plus every scripts/*.sh named by run_all.sh — with the
clj-requiring dev tools exempt by explicit list. The e2e itself moves to
run_bounded + bash SECONDS. Local-vs-CI parity is a check, not a memory.
run_gate's default timeout rises 600 -> 900 s: a cold-cache serial full gate
measured over 600 (the two zig build test steps alone were 271 s), and a
timeout that kills a healthy gate teaches the wrong lesson. Warm gate: 283 s.
Pre-tag cadence run: full gate 429/0, lib_conformance --all regenerated
COVERAGE.md, verify_projects 19/19.
Smell-audited: 2: the user asked whether CI was actually green — it was not,
and the divergence class already had a precedent and an unused in-repo fix.
The guard makes the class mechanical rather than remembered, per the same
posture as check_epipe_head / gate_parity.
0 commit comments