[automated] Monitor selective PR CI accuracy after enforcement #19787

Activity

1. github-actions

   added

   needs-area-labelAn area label is needed to ensure this gets routed to the appropriate area ownersAn area label is needed to ensure this gets routed to the appropriate area owners

   on Aug 28, 2026
2. Ankit Jain (radical)

   added a parent issue on Aug 28, 2026

   • [automated] Improve PR CI time with selective test execution #19757
3. Ankit Jain (radical)

   added

   area-engineering-systemsinfrastructure helix infra engineering repo stuffinfrastructure helix infra engineering repo stuff

   and removed

   needs-area-labelAn area label is needed to ensure this gets routed to the appropriate area ownersAn area label is needed to ensure this gets routed to the appropriate area owners

   on Aug 28, 2026
4. joperezr commented on Aug 28, 2026

   

   Jose Perez Rodriguez (joperezr)

   on Aug 28, 2026

   Member

   More actions

   🤖 Aspire triage pass — 2026-08-28 22:33 UTC

   Area: area-engineering-systems
   Kind: feature-request (internal CI rollout audit / monitoring task)
   Repro: none — monitoring/audit tracking issue for the rollout enabled by #19688
   Affected version(s): N/A — internal CI infrastructure (not a shipped product surface)
   Severity: S4 — monitoring/accuracy audit of selective PR test execution; internal tooling

   Urgency: ⚪ backlog — no milestone
   Reason: bounded internal rollout audit tracked against #19757; not a regression or customer-facing bug

   Suggested owner(s): David Pine (@IEvangelist) (score 24), backup Adam Ratzman (@adamint) (score 12)
   Evidence:

   • IEvangelist merged Fix docs safe-output base resolution #19446, Fix gh-aw v0.86.2 safe-output base parsing #19445, Upgrade gh-aw compiler to v0.86.2 #19438, Fix PR docs recovery base handling #19236 in area-engineering-systems (last 90d, 8 PRs)
   • adamint merged Remove pipeline-scoped Publish-Build-Assets group #19518, Avoid MongoDB credential false positive #19305, Re-enable VS Code extension E2E tests in CI #19142 in area-engineering-systems (last 90d, 4 PRs)
   • (issue author excluded from owner scoring; no file paths cited so CODEOWNERS not scored)

   Confidence: medium
   Needs human?: no
5. Jose Perez Rodriguez (joperezr)

   added

   triage:bot-seenAspire triage bot has seen this issueAspire triage bot has seen this issue

   on Aug 28, 2026
6. Ankit Jain (radical)

   removed a parent issue on Aug 29, 2026

   • [automated] Improve PR CI time with selective test execution #19757
7. Ankit Jain (radical)

   added a parent issue on Aug 29, 2026

   • Tracking: Make Aspire CI reliable, actionable, and efficient #18036
8. radical commented on Sep 8, 2026

   

   Ankit Jain (radical)

   on Sep 8, 2026

   MemberAuthor

   More actions

   [automated] Follow-up found during continued monitoring: #19986 tracks benchmark projects outside the Aspire.slnx graph that are currently reported as unattributed and conservatively fall back to ALL.

   Run 34247134578 exposed the gap without losing coverage because Directory.Packages.props independently selected ALL.
9. radical commented on Oct 1, 2026

   

   Ankit Jain (radical)

   on Oct 1, 2026

   MemberAuthor

   More actions

   [automated] The bounded rollout audit reached its 50-eligible-run limit and is complete.

   At the published 42-run checkpoint, 30 runs selected a subset and 12 selected ALL, with no observed false positives or false negatives. The remaining eight runs completed the bound without a selector-safety escalation.

   Safe over-selection and diagnostic follow-ups remain tracked in #19786 and #19986. Ongoing selection-drift monitoring is tracked by #20324.

   Closing this bounded rollout audit; program-level CI work continues in #18036.
10. Ankit Jain (radical)

    closed this as completedon Oct 1, 2026
11. github-actions

    locked and limited conversation to collaborators on Oct 31, 2026