Repository navigation
[ci-scan-feedback] KPI Tracker #7621
Description
(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-07-03T04:09:47Z
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 99 runs since the window opened on 2026-06-08T13:53:53Z. No [ci-scan] KBE issues have been filed. The persistent skip reason is stale build window (>14d): MachineLearning-CI (definition 167, main) has had no new failed build since build #1453653 (2026-06-08), now ~25 days ago. The CI appears healthy — the absence of KBEs is expected.
Latest two ci-scan runs:
- Run publish symbols enabled #99 (2026-07-03T01:05:10Z, success):
stale build window (>14d)+no follow-up build yet— all skip conditions satisfied; no KBE issues filed. - Run Support for HDF5? #98 (2026-07-02T18:58:55Z, success):
stale build window (>14d)— tally:total-signatures=0, issues-filed=0, reused-existing=0, skipped-with-reason=1✓
This tick: No PR opened. Scanner behavior is correct — it exits early with the right skip reasons and accurate tally. No [ci-scan] KBE issues have been filed, so rubric scoring has zero rows. No maintainer feedback exists to translate into prompt edits.
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) · ● 4.6M · ◷
Activity