Skip to content

Instantly share code, notes, and snippets.

Show Gist options
  • Select an option

  • Save jaredpar/32bcfc15dcfb5f45566f99527d667db4 to your computer and use it in GitHub Desktop.

Select an option

Save jaredpar/32bcfc15dcfb5f45566f99527d667db4 to your computer and use it in GitHub Desktop.

Health Report β€” dotnet/roslyn / roslyn-integration-lsp-CI

Overall Health: πŸ”΄ RED β€” PIPELINE NON-OPERATIONAL (60+ HOURS)

Current Status:

  • PIPELINE DOWN β€” 0% success rate, 9/9 builds failed, 0 builds attempted in 60+ hours
  • Last build: 2026-05-16 07:04 AM PDT
  • No new builds since β€” pipeline disabled or trigger broken
  • Builds fail pre-test β€” no test execution occurs, no timeline data retrievable
  • Affected: 9 PRs from 6 different authors were blocked

Active Problems:

# Problem Started Duration Severity
1 Pipeline completely non-functional β€” all builds fail before test execution 2026-05-16 07:00 AM PDT 60+ hours πŸ”΄ CRITICAL
2 No builds queued/attempted since failure burst β€” pipeline likely disabled 2026-05-16 07:04 AM PDT 60+ hours πŸ”΄ CRITICAL
3 Timeline API returning empty responses (blocks root cause diagnosis) 2026-05-16 60+ hours 🟑 MEDIUM

Root Cause Hypothesis:

  • 9 unrelated PRs failing simultaneously within 4 minutes = infrastructure/pipeline configuration failure
  • roslyn-integration-CI healthy β†’ issue is specific to LSP pipeline definition (not shared infra)
  • Zero test data + abandoned timelines β†’ builds die at a very early stage
  • Known issues #83287 (VSIXInstaller) and #83177 (VsixUtil.exe) remain candidates but cannot be confirmed
  • Pipeline appears to have been disabled after the batch failure

Recently Resolved Issues:

  • None β€” no recovery detected

Trends:

  • ❌ NO CHANGE from previous evaluation β€” RED for 60+ hours with no recovery
  • ❌ NO NEW BUILD ATTEMPTS β€” pipeline remains dormant
  • βœ… Sibling pipeline roslyn-integration-CI remains fully green (20/20 today)

Confidence Level: 🟑 MEDIUM

  • βœ… High confidence: pipeline is non-functional (clear from 9/9 failures)
  • βœ… High confidence: isolated to LSP pipeline (sibling is green)
  • ❌ Low confidence: root cause unknown (no timeline/log data)
  • ❌ Cannot determine if disabled vs. trigger misconfigured

Required Actions:

  1. IMMEDIATE: Check if pipeline is disabled in Azure DevOps β€” Pipeline link
  2. IMMEDIATE: Manually inspect build logs in AzDO UI for build 1423349 β€” API data is unavailable
  3. Compare pipeline YAML between roslyn-integration-CI (working) and roslyn-integration-lsp-CI (broken)
  4. Re-enable pipeline and trigger a manual test build to verify recovery

Last Updated: 2026-05-18 22:41 PDT

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment