Repository navigation
Description
Summary
- CI failure rate (last 20 runs of
ci.yml): 3/20 = 15% (11 success, 6 cancelled, 3 failure) - Consecutive failure streak: None — failures are interspersed with successes/cancellations, no back-to-back failure run.
- Recommended action: Investigate — one recurring pattern (lock-file drift) appeared in 2 of the 3 failed runs and is a real regression risk if lock files aren't kept in sync with markdown sources.
Failure Details
Pattern 1 — Workflow lock file drift (2 of 3 failed runs: run #52856 / #52854)
Job Check workflow markdown/lock drift fails with:
ERROR: Workflow lock files are out of sync with their markdown sources.
.github/workflows/smoke-cursor.lock.yml
This indicates .github/workflows/smoke-cursor.md was edited without running make recompile before commit, so the generated .lock.yml no longer matches. This is a consistent, reproducible regression pattern (not flaky) tied to a specific lock file.
Pattern 2 — Go module proxy 403 (1 of 3 failed runs: run #52851)
Job health-smoke-copilot fails during make build:
##[error].../go-sdk@v1.7.0/.../json.go:13:2: github.com/segmentio/encoding@v0.5.4: reading (proxy.golang.org/redacted) 403 Forbidden
This looks like a transient/external Go module proxy issue rather than a code regression — flaky infrastructure dependency, not a code defect.
Open bug-labeled issues (no issues currently carry both bug + regression labels; showing top bug-labeled open issues for context):
- eslint-factory: require-error-code-for-github-api-throw does not recognize octokit.request() calls #58933 — eslint-factory: require-error-code-for-github-api-throw does not recognize octokit.request() calls
- pushSignedCommits fallback pushes stale branch ref after rebasing detached HEAD #58910 — pushSignedCommits fallback pushes stale branch ref after rebasing detached HEAD
- [WIP] Smoke Project: work in progress #57272 — [WIP] Smoke Project: work in progress
- [Firewall Test] Escape test failed #57063 — [Firewall Test] Escape test failed
None of these open issues appear to directly correspond to the two failure patterns above (lock-file drift, Go proxy 403), so no existing regression issue tracks either.
Generated by 🧭 Daily Regression Audit · copilot · auto · 78.3 AIC · ⌖ 7.47 AIC · ⊞ 7.1K · ◷
- expires on Sep 11, 2026, 6:39 PM UTC-08:00
Activity
github-actions commentedon Sep 11, 2026
This issue is being closed as outdated. A newer issue has been created: #60147
View newer issue
This action was performed automatically by the
Daily Regression Auditworkflow.