renders the header when the profile payload is partial
chromium · 2 runs analysed · 1 failed · 1 pass/fail flips · unknown rule matched
What happened. Deterministic findings across 2 CI runs — the same answer every time. No AI involved yet.
1 passed · 1 failed
Failed in 1 of 2 runs
No retry recovery observed
Outcome changed between runs
Execution history
Outcome changed 1 time across 2 runsFailure pattern
Failure type could not be determined
Could not confidently determine a specific root cause — this failure needs a manual look
This test failed with an error that doesn't match any known Playwright pattern. Manual investigation with traces and screenshots is the best next step.
Similar failures
2 other tests show a similar failure pattern
Browsers
Error detail
No structured error was captured for this failure.
Failure behaviour
- Failed in latest run (Run 2)
- Passed in previous run (Run 1)
How certain the analyzer is
- Mixed results — recovered on retry in at least one run
- 2 other test(s) share this failure fingerprint (some corroboration)
- Only 2 run(s) analyzed (limited data)
Not captured for this failure: failure type, error, code location, retry behaviour.
The rules established the facts. Now ask what they mean.
The deterministic engine says what happened. AI weighs those signals against each other to attribute the failure — and may disagree, hedge, or decline.