[ci-scan-feedback] KPI Tracker

[github-actions]

(ci-scan-feedback-window-start)2026-05-21T01:26:48Z(/ci-scan-feedback-window-start)

Tracking quality of [ci-scan] (detection) and [ci-fix] (mitigation) issues, PRs, and loop-in comments since 2026-05-21T01:26:48Z. Updated every tick of ci-failure-scan-feedback.lock.yml. To raise a concern, comment here or on any [ci-scan]/[ci-fix] issue/PR; 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-13T10:25:00Z

Activity (last 7d)

stream	opened	good	wrong/unmerged
Scanner KBE issues	8	0	0
Fixer [ci-fix] PRs (confident)	0	0	0
Fixer [ci-fix] PRs (help-wanted)	5	0	0
Fixer loop-in comments	0	0 engaged	—

"good" = KBEs closed completed, PRs merged, loop-ins with a maintainer reply. "wrong/unmerged" = KBEs closed not_planned/duplicate, PRs closed without merge (note: a help-wanted PR closed unmerged is expected, not necessarily a miss).

Scanner quality (last 30d)

metric	count	rate
KBE closures	1	—
Wrong KBE closures	0	n/a (1<10)
Maintainer rejection comments	0	—
Duplicate KBEs	0	—

Fixer quality (last 30d)

metric	count	rate
Fix PR closures	0	—
Fix PRs merged	0	—
Fix PRs rejected (maintainer pushback)	0	n/a (0<5)
Loop-in comments (posted / engaged)	0 / 0	—
Loop-in / help-wanted mis-attributions	0	—

Fixer active with 8 runs (7 success, 1 failure). Five open help-wanted PRs: #129212 (ReflectionMemberAccessor unwrap), #129235 (TensorPrimitives tolerance), #129314 (ByRefLike process isolation), #129328 (PolymorphicTests ordering), #129360 (StreamReader bufferSize PGO). PR #129212 received constructive review from @jkotas suggesting BindingFlags.DoNotWrapExceptions as a simpler approach — quality signal for fixer to prefer existing framework mechanisms over manual patterns.

Outage signals (analyzed CI)

signal	threshold	24h	7d	status
New-KBE burst	day > 2x trailing 30d median (min 3)	3 / median 0	peak day 2	🟢
Build-break spike	>= 2 in any 24h	0	0 max	🟢
Multi-pipeline outage (distinct legs proxy)	>= 3 distinct legs in 24h	2 distinct	2 distinct (peak Jun 13)	🟢
KBE re-filed after maintainer close	any in 7d	1	2	🔴
Scanner wrong-closure rate (30d)	>= 30% with scan_closed_30d >= 10	—	n/a (1<10)	🟢
Fixer rejection rate (30d)	>= 30% with fix_closed_30d >= 5	—	n/a (0<5)	🟢

details: KBE re-filed after maintainer close — #129327 re-filed #128899 (PInvokeUnhandled assert recurrence in runtime-interpreter, predecessor closed completed Jun 3); #129210 re-filed #128993 (X509Certificate2CollectionRemoveRangeArray crossgen2, predecessor closed completed Jun 5)

[Filtered] count: 0

Note

🔒 Integrity filter blocked 1 item

The following item was blocked because it doesn't meet the GitHub integrity level.

• #128501 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

Generated by CI Outer-Loop Failure Scanner — Feedback · ● 16M · ◷

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.