[ci-scan-feedback] Reject shared-console-log suite-harness KBE signatures #133080

Triggering signals

• KBE [ci-scan] Test failure: profiler/gc/nongcheap/nongcheap.cmd fails with missing 'PROFILER TEST PASSES' #131449 — MEMBER janvorli (2026-08-07): "This issue seems to be a kitchen sink for all kinds of profiler tests failures." [ci-scan] Test failure: profiler/gc/nongcheap/nongcheap.cmd fails with missing 'PROFILER TEST PASSES' #131449 (comment)
• KBE [ci-scan] Test failure: profiler/gc/nongcheap/nongcheap.cmd fails with missing 'PROFILER TEST PASSES' #131449 — MEMBER noahfalk (2026-08-22): re-scoped the KBE so it "only matches nongcheap.cmd. Previously the KBE matched the Helix console log which runs many tests. Whenever some other profiler test failed the [signature matched]." [ci-scan] Test failure: profiler/gc/nongcheap/nongcheap.cmd fails with missing 'PROFILER TEST PASSES' #131449
• Rubric finding: the array signature paired a per-invocation Running test: ...nongcheap.cmd announcement with a suite-wide harness error (PROFILER TEST PASSES missing); both co-exist in the profiler suite's single shared Helix console log, so the KBE matched whenever any profiler/** test failed. A prior tracker snapshot claimed this class was addressed, but no [ci-scan-feedback] PR actually landed the rule.

Proposed edits

• .github/workflows/shared/create-kbe.instructions.md (Signature specificity → reject list, ~line 530): add a reject bullet for signatures pairing a per-invocation announcement line with a suite-wide harness error that share one console log — tied to the [ci-scan] Test failure: profiler/gc/nongcheap/nongcheap.cmd fails with missing 'PROFILER TEST PASSES' #131449 kitchen-sink signal.
• .github/workflows/shared/create-kbe.instructions.md (Bad vs good signatures table, ~line 556): add a Bad/Good row using the concrete gcheapenumeration profiler case, showing the anchor should be the failing test's own error output from a per-test log source rather than the harness aggregate.

Expected behavior change

The next scanner run will refuse to build a KBE signature from a per-invocation announcement line combined with a shared-harness pass/fail summary when both live in one suite-wide console log, avoiding the over-broad "kitchen sink" KBE that matches every unrelated failure in the same test suite.

Generated by CI Outer-Loop Failure Scanner — Feedback · opus48 · 369.3 AIC · ⌖ 25.3 AIC · ⊞ 20.6K · ◷

To create a pull request with the changes:

# Download the artifact from the workflow run
gh run download 33632772611 -n agent -D /tmp/agent-33632772611

# Fetch the bundle into a temporary ref, then update the local branch
git fetch /tmp/agent-33632772611/aw-ci-scan-feedback-shared-console-log-signature.bundle refs/heads/ci-scan-feedback-shared-console-log-signature:refs/bundles/create-pr-ci-scan-feedback-shared-console-log-signature-ecfc2f9d38a585eb-d685b77d
git update-ref refs/heads/ci-scan-feedback-shared-console-log-signature-ecfc2f9d38a585eb refs/bundles/create-pr-ci-scan-feedback-shared-console-log-signature-ecfc2f9d38a585eb-d685b77d
git checkout ci-scan-feedback-shared-console-log-signature-ecfc2f9d38a585eb
# Ensure the working tree matches the updated branch
git reset --hard
# Remove the temporary bundle ref
git update-ref -d refs/bundles/create-pr-ci-scan-feedback-shared-console-log-signature-ecfc2f9d38a585eb-d685b77d

# Push the branch to origin
git push origin ci-scan-feedback-shared-console-log-signature-ecfc2f9d38a585eb

# Create the pull request
gh pr create --title '[ci-scan-feedback] Reject shared-console-log suite-harness KBE signatures' --base main --head ci-scan-feedback-shared-console-log-signature-ecfc2f9d38a585eb --repo dotnet/runtime