Skip to content

Instantly share code, notes, and snippets.

@jaredpar

jaredpar/dotnet-roslyn-roslyn-CI-health.md

Created June 23, 2026 14:57
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save jaredpar/34476193f3f3c1bbd352be9681c7d5e4 to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save jaredpar/34476193f3f3c1bbd352be9681c7d5e4 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
dotnet-roslyn-roslyn-CI-health.md

Health Report — dotnet/roslyn / roslyn-CI

Generated: 2026-06-22 14:15 | Window: 3 days

Generated: 2026-06-22 2:14 PM PT | Window: 3 days

Overall Health: 🟡 YELLOW

CI pass rate (main): 3 succeeded / 5 failed in last 3 days. The 2-consecutive-green streak (builds 1475831, 1475968) was broken by build 1476004 which failed due to a test host crash and a 120-minute job timeout.

Active Problems

Problem Since Severity Trend
Helix work item crashes (workitem_0, _6, _39, _43) ~10+ days ago 🟡 Medium Chronic — infrastructure issue, not worsening
Test_Windows_CoreClr_Debug_Single_Machine 120-min timeout Jun 20 (recurred Jun 22) 🟡 Medium Intermittent — appeared resolved but recurred in build 1476004
Fuzz_2 test host crash (build 1476004) Jun 22 🟠 Watch New — first occurrence, monitoring for recurrence

Known Issue Correlations

  • None of the 6 active known issues matched failures in this window.

Recently Resolved

  • Main branch failure streak (Jun 19–22): Partially resolved — 2 green builds occurred but streak broken again by 1476004.

Recommended Actions

  1. Monitor Fuzz_2 crash: If it recurs, investigate the dump file and consider filing a Known Build Error. Use tiger azdo download-dumps 1476004 to retrieve the crash dump.
  2. Investigate recurring 120-min timeout on Test_Windows_CoreClr_Debug_Single_Machine: This job is intermittently hitting the time limit. May need timeout increase or investigation into what's causing slowness on NetCore-Public 107.
  3. Helix work item crashes: Continue tracking. Consider filing an infrastructure Known Build Error in dotnet/dnceng if a common error pattern can be extracted.

Trends

  • Unstable YELLOW: Main branch alternates between green and infrastructure-caused failures.
  • Zero real CI test failures: All actual test failures remain PR-only. Merged code quality is excellent.
  • Upgrade to GREEN if: Next 2+ main builds pass without timeout/crash issues.
  • Stay YELLOW if: Timeouts or crashes continue intermittently.
  • Downgrade to RED if: Real test failures appear on main, or timeouts become every-build.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment