Summary
- CI failure rate (last 20 completed runs of
ci.yml): 10 failures / 20 = 50% (5 success, 5 cancelled)
- Consecutive failure streak: none strict. Newest runs are failure, cancelled, cancelled, failure, then 2 successes. Cancelled runs are mostly superseded pushes.
- Recommended action: investigate. Failure rate is well above 10% and the most recent main push failed.
Failure Details
Pattern 1: Pi safe-outputs prompt test (new, most recent push)
Run 37088817818 (push to main, "Upgrade Pi to v1 and integrate non-TUI engine capabilities (#65188)") failed in pkg/workflow:
--- FAIL: TestPiSafeOutputsPromptStatesCLIIsOnlyTransportIntegration- Package-level failure:
FAIL github.com/github/gh-aw/pkg/workflow
This is likely a regression from #65188 and is a deterministic failure.
Pattern 2: Earlier failures on 2026-10-02 (20:16–22:15 UTC)
Eight consecutive failing runs (push and schedule) were seen before run 37073430692 ("Fix main CI setup-cli and linter metadata failures (#65125)") succeeded. This suggests a main-branch breakage that was fixed. The failure for run 37071455426 was found, but its job logs were no longer available (the tool reported 0 failed jobs), so the root cause was not independently confirmed.
Pattern 3: Scheduled run 37089635647
Failed overall, but no failed jobs were reported among 30 jobs. This may be a flaky or infrastructure failure. Needs a re-check.
Open regression/bug issues
Query for open bug + regression issues returned 5 results, but all were hidden by the integrity filter and cannot be listed: #65189, #63926, #63924, #63775, #63559.
Generated by 🧭 Daily Regression Audit · copilot · auto · 25.2 AIC · ⌖ 5.06 AIC · ⊞ 8K · ◷
Summary
ci.yml): 10 failures / 20 = 50% (5 success, 5 cancelled)Failure Details
Pattern 1: Pi safe-outputs prompt test (new, most recent push)
Run 37088817818 (push to main, "Upgrade Pi to v1 and integrate non-TUI engine capabilities (#65188)") failed in
pkg/workflow:--- FAIL: TestPiSafeOutputsPromptStatesCLIIsOnlyTransportIntegrationFAIL github.com/github/gh-aw/pkg/workflowThis is likely a regression from #65188 and is a deterministic failure.
Pattern 2: Earlier failures on 2026-10-02 (20:16–22:15 UTC)
Eight consecutive failing runs (push and schedule) were seen before run 37073430692 ("Fix main CI setup-cli and linter metadata failures (#65125)") succeeded. This suggests a main-branch breakage that was fixed. The failure for run 37071455426 was found, but its job logs were no longer available (the tool reported 0 failed jobs), so the root cause was not independently confirmed.
Pattern 3: Scheduled run 37089635647
Failed overall, but no failed jobs were reported among 30 jobs. This may be a flaky or infrastructure failure. Needs a re-check.
Open regression/bug issues
Query for open
bug+regressionissues returned 5 results, but all were hidden by the integrity filter and cannot be listed: #65189, #63926, #63924, #63775, #63559.