(window_start)2026-06-08T13:53:53Z(/window_start)
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-26T04:07:00Z
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: The ci-scan workflow has completed 71 runs since the window opened on 2026-06-08T13:53:53Z. No [ci-scan] KBE issues have been filed. The persistent skip reason remains stale build window (>14d) / no follow-up build yet, defer to next run: MachineLearning-CI (definition 167, main) has had no build complete since build #1453653 (failed, 2026-06-08), now 18 days ago.
Latest two runs:
No new rubric signal or maintainer feedback to act on this tick; Step 6 (PR edit) skipped. The "Hard Rule 10" early-exit proposal exists as 10 open duplicate issues (#7627, #7630, #7636, #7637, #7639, #7640, #7641, #7642, #7643, #7644) from past git-push failures; maintainer action required to clean those up.
Rubric scorecard: zero rows (no [ci-scan] KBE issues exist to score).
| run-id |
issue |
title-scoped |
classification |
match-specific |
occurrence-honest |
log-cross-check |
maintainer-feedback |
| (no rows — zero KBE issues filed since window-start) |
|
|
|
|
|
|
|
[Filtered] count: 0
Generated by CI Failure Scanner - Feedback (machinelearning)
Generated by CI Failure Scanner - Feedback (machinelearning) · ● 1.9M · ◷
(window_start)2026-06-08T13:53:53Z(/window_start)
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-26T04:07:00Z
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: The
ci-scanworkflow has completed 71 runs since the window opened on 2026-06-08T13:53:53Z. No[ci-scan]KBE issues have been filed. The persistent skip reason remainsstale build window (>14d)/no follow-up build yet, defer to next run:MachineLearning-CI(definition 167,main) has had no build complete since build #1453653 (failed, 2026-06-08), now 18 days ago.Latest two runs:
stale build window (>14d)/no follow-up build yet, defer to next run— tally:| 0 | 0 | 0 | 0 || 0 | 0 | 0 | 0 |No new rubric signal or maintainer feedback to act on this tick; Step 6 (PR edit) skipped. The "Hard Rule 10" early-exit proposal exists as 10 open duplicate issues (#7627, #7630, #7636, #7637, #7639, #7640, #7641, #7642, #7643, #7644) from past git-push failures; maintainer action required to clean those up.
Rubric scorecard: zero rows (no
[ci-scan]KBE issues exist to score).[Filtered] count: 0