Generated: 2026-06-23 08:34 | Window: 3 days
Generated: 2026-06-23 8:33 AM PT | Window: 3 days
Overall Health: 🟡 YELLOW
CI pass rate (main): 5 succeeded / 10 failed since Jun 20. Latest build 1477299 succeeded (Jun 23 8:02 AM PT). Prior failure 1477021 was timeout-only.
| Problem | Since | Severity | Trend |
|---|---|---|---|
Test_Windows_CoreClr_Debug_Single_Machine 120-min timeout |
Jun 20 | 🔴 High | Persistent — 5 hits in 3 days, caused by Helix queue backups on NetCore-Public agents |
| Razor AddImport code action tests (12 tests) | Jun 22 | 🟡 Medium | Active — tracked by #83775 |
| Helix work item crashes (workitem_6, _39, _40, _43) | ~10+ days | 🟡 Medium | Chronic — steady background rate, not worsening |
- #83775 actively matching Razor AddImport failures (2 CI builds + 1 PR build).
- No other known issues triggered in this window.
- Latest CI build passed: 1477299 succeeded on main (Jun 23 8:02 AM PT), indicating that when Helix queues are healthy, the build passes cleanly.
- 🔴 File Known Build Error for timeout: Pattern
ran longer than the maximum time of 120 minuteswithBuildRetry: true— this would auto-retry the most common CI failure mode. - 🔴 Escalate Helix queue capacity: 5 timeouts in 3 days on different
NetCore-Publicagents is a systemic problem. File indotnet/dnceng. - Razor AddImport: Tracked by #83775 — no additional action.
- Monitor "Helix completed without specifying a job id": Single occurrence — watch for recurrence before filing.
- Holding at YELLOW: The timeout issue remains the dominant failure mode but is intermittent — latest build passed.
- Zero non-Razor real CI test failures: Merged code quality is excellent.
- Upgrade to GREEN if: 3+ consecutive main builds pass without timeout.
- Return to RED if: Timeout recurs in next 2 builds or a new failure mode emerges.