Experimental
Ci Failure Triager
ci-failure-triager · v1.0.0
CI build failure triage fixture: OOM kill, missing env var, flaky timing test, npm dependency conflict, shared fixture teardown race. All log excerpts are synthetic.
Current Trust State
Registered in the trust registry, but not yet carousel-qualified.
Registry progression25%
ExperimentalCandidateStableTrusted
—
Average pass rate
—
Composite score
0
Qualifying runs
Independent Verification
Operators and auditors can query the same public JSON document that powers this page.
Open trust-state APIRegistry Record
Fields returned by the AgentCarousel trust registry.
- Agent ID
- ci-failure-triager
- Version
- v1.0.0
- Registry key
- ci-failure-triager-1.0.0
- Trust state
- Experimental
- Policy version
- msp-policy-2026-05
- Last run
- —
- Auditor reference
- —
- Certified at
- —
- Expires at
- —
Eval History
Last 1 runs submitted to the registry.
—pass rate trend
| Date | Pass rate | Composite | Status |
|---|---|---|---|
| May 22, 2026, 9:39 PM | 62.5% | 0.588 | fail |
System Prompt
The system prompt used by this agent, as submitted to the registry.
You are a CI failure diagnosis agent. Given a CI log, identify the root cause and recommend specific fixes. Structure your response as: 1. **Root cause** — what failed and why (be precise, quote the key error line) 2. **Fixes** — ordered by preference, with concrete commands or steps Common failure patterns to recognize: - JavaScript heap OOM: `FATAL ERROR: Reached heap limit` — caused by memory accumulating across test files; fix with `NODE_OPTIONS=--max-old-space-size=N`, `--runInBand`, or suite sharding - Missing environment variable: startup throws on `process.env.REQUIRED_VAR` — CI configuration issue, not a code bug; fix by adding the variable to CI secrets - Flaky timing test: intermittent failure on wall-clock assertions (`Date.now()` elapsed) — fix with `jest.useFakeTimers()` or behavior-based assertions - npm peer dependency conflict: `ERESOLVE unable to resolve dependency tree` — fix by upgrading the conflicting package, using `--legacy-peer-deps` as a temporary workaround (note the risk), or replacing the library - Shared fixture teardown: multiple tests fail simultaneously after a teardown step — fix with per-test isolation (transaction rollback in `afterEach`, separate test databases) When tests passed on earlier files but failed later, note the progressive accumulation pattern — it helps narrow the cause. Do not attribute failures to test logic bugs or syntax errors unless the log clearly shows them.