[regression] Daily CI Regression Audit — 36211879919

[github-actions]

Summary

• CI failure rate (last 20 completed runs of ci.yml): 4/20 = 20% (failure), plus 2 cancelled runs
• Consecutive failure streak: Yes — 3 in a row (runs [daily regulatory] Regulatory Report - 2026-08-24 #55519, Deduplicate token-usage and integrity-level types flagged by Typist #55518, [aw] Test Quality Sentinel reported incomplete result #55517, all on main, 2026-09-25 ~21:36–22:14 UTC), interrupted by a cancelled run before returning to green
• Recommended action: Monitor — the streak is resolved (16 of last 16 runs since are green) and one failure mode is a flaky upstream network error, not a code regression. The recurring "workflow lock drift" failure is worth a quick look if it recurs again, but is self-resolving (fixed by recompile) rather than a code regression.

Failure Details

Runs inspected (20 most recent completed ci.yml runs on main):

Run #	Conclusion	Created
55523	success	2026-09-26 02:20
55522	success	2026-09-26 01:24
55521	success	2026-09-26 00:42
55520	success	2026-09-25 23:13
55519	failure	2026-09-25 22:14
55518	failure	2026-09-25 21:48
55517	failure	2026-09-25 21:36
55516	cancelled	2026-09-25 21:33
55515	success	2026-09-25 21:13
55514	failure	2026-09-25 20:52
55513–55504	success/cancelled	earlier

Top failure patterns (from job logs of the 3 most recent failed runs):

1. "Check workflow markdown/lock drift" job — ERROR: Workflow lock files are out of sync with their markdown sources.
   Appeared in run [daily regulatory] Regulatory Report - 2026-08-24 #55519 (job 108271721079) and run [aw] Test Quality Sentinel reported incomplete result #55517 (job 108261211031). This is a compile-drift check that fails when .lock.yml files aren't regenerated after a .md workflow source change — deterministic, not flaky, but self-resolved by running make recompile before merge. No evidence of a code regression in the compiler itself; likely a contributor forgetting to recompile before pushing.

2. "Integration Unauthenticated Add (Public Repo)" job — go mod download transient network failure
   In run Deduplicate token-usage and integrity-level types flagged by Typist #55518 (job 108264205808): go: golang.org/x/crypto@v0.57.0: read "(proxy.golang.org/redacted) stream error: stream ID 511; INTERNAL_ERROR; received from peer. This is a Go module proxy HTTP/2 stream reset — a classic transient network flake unrelated to any code change. No repeat of this specific error in the other two failed runs, so it does not appear to be a systemic regression.

3. "Integration Compile gh-aw-marketplace" job — skipped in all three failed runs. Not a failure by itself; likely gated behind other jobs that failed upstream in the same run, so it never executed.

No new/novel error signatures were observed beyond these two known patterns (lock drift and Go proxy flake). Both are consistent with historical noise rather than an emerging regression.

Open regression/bug issues (bug + regression labels, open, up to 5): No issues could be read — all 5 candidate results (#63438, #63435, #63434, #63351, #63186) were filtered by integrity policy before their labels/content could be confirmed as matching bug+regression, so their exact status here is unconfirmed and not included in this audit's failure-pattern analysis.

Generated by 🧭 Daily Regression Audit · copilot · auto · 42.3 AIC · ⌖ 5.36 AIC · ⊞ 8.1K · ◷

• expires on Sep 27, 2026, 6:34 PM UTC-08:00