Tracking quality of [ci-scan] issues since 2026-06-08T13:53:53Z. Updated every tick of ci-scan-feedback.agent.lock.yml. To raise a concern, comment on any [ci-scan] issue; the next tick reads in-scope feedback and either opens a [ci-scan-feedback] PR with prompt edits or pushes to the existing one.
Snapshot - 2026-06-09T04:05:56Z
Activity (last 7d)
| artifact |
opened |
closed (good) |
closed (wrong) |
| Issues |
0 |
0 |
0 |
"closed (good)" = closed completed. "closed (wrong)" = closed not_planned/duplicate.
Quality (last 30d)
| metric |
count |
rate |
| Total closures |
0 |
- |
| Wrong closures |
0 |
n/a (0<10) |
| Maintainer rejection comments |
0 |
- |
| Duplicate KBEs |
0 |
- |
Outage signals (analyzed CI)
| signal |
threshold |
24h |
7d |
status |
| New-KBE burst |
day > 2x trailing 30d median (min 3) |
0 / median 0 |
peak day 0 |
🟢 |
| Build-break spike |
>= 2 in any 24h |
0 |
0 |
🟢 |
| KBE re-filed after maintainer close |
any in 7d |
0 |
0 |
🟢 |
| Wrong-closure rate (30d) |
>= 30% with closed_30d >= 10 |
- |
n/a (0<10) |
🟢 |
Notes for this snapshot: This is the first tick. The ci-scan workflow has run 3 times (runs #27142521282, #27161096107, #27177757444), all with success/noop - no Known Build Error issues have been filed yet, which means either MachineLearning-CI has been green or all candidates were filtered by the stability/follow-up gate. All outage signals are 🟢 by virtue of zero KBE volume. The rubric scorecard has zero rows (nothing to score). Integrity-filtered: 0.
Generated by CI Failure Scanner - Feedback (machinelearning) · ● 3.9M · ◷
Tracking quality of
[ci-scan]issues since 2026-06-08T13:53:53Z. Updated every tick of ci-scan-feedback.agent.lock.yml. To raise a concern, comment on any[ci-scan]issue; the next tick reads in-scope feedback and either opens a[ci-scan-feedback]PR with prompt edits or pushes to the existing one.Snapshot - 2026-06-09T04:05:56Z
Activity (last 7d)
"closed (good)" = closed
completed. "closed (wrong)" = closednot_planned/duplicate.Quality (last 30d)
Outage signals (analyzed CI)
closed_30d >= 10Notes for this snapshot: This is the first tick. The
ci-scanworkflow has run 3 times (runs #27142521282, #27161096107, #27177757444), all withsuccess/noop - noKnown Build Errorissues have been filed yet, which means eitherMachineLearning-CIhas been green or all candidates were filtered by the stability/follow-up gate. All outage signals are 🟢 by virtue of zero KBE volume. The rubric scorecard has zero rows (nothing to score). Integrity-filtered: 0.