Repository navigation
[detection-analysis] Detection Analysis Report — 2026-10-08 #67024
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by Detection Analysis Report. A newer discussion is available at Discussion #67301. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Summary
2026-10-07T23:32Z→2026-10-08T23:32Zaw_info.json): 177gh-aw-detection: false): 1 (0.6% of classifiable)Note
No misconfigured
gh-aw-detectionworkflows were identified in this window. All three misconfiguration rules (persistent opt-out on a high-volume workflow, a failingdetectionjob, and flag-alternation within the window) came back clean.Comparison Chart
Detection-enabled runs: 176 runs, 82.4% success rate, 144,909 avg tokens.
Regular runs: 1 run, 0% success rate, 382,645 avg tokens — a single data point (Smoke Agy (Experimental)), not statistically comparable to the 176-run detection cohort.
Misconfigured Workflows
No misconfigured workflows detected in this window.
View All Run Metrics
Full dataset: 41 distinct workflows, 177 classifiable runs. Single-run workflows aren't meaningfully comparable on success rate; they're included for completeness.
Excluded from classification (117 runs across
ai-moderator,aw-failure-investigator,daily-trajectory-grader-implementer,pr-sous-chef,test-quality-sentinel, smoke-copilot variants,avenger,visual-regression-checker, and others): these run directories only contained the raw GitHub Actionsrun.jsonwith noaw_info.json/run_summary.json, so the detection flag and token usage could not be recovered. 57 succeeded, 53 failed, 7 were still in-progress/queued at snapshot time.View Historical Trend
Detection run volume has declined from a peak of ~430 runs/day in mid-September to ~176 today, while detection success rate has climbed from ~35–50% to 82% over the same period. Regular (opted-out) run volume stays consistently low to zero.
Recommendations
gh-aw-detectionconfiguration — the feature is enabled by default across essentially the whole fleet (176/177 classifiable runs) and no workflow shows a failingdetectionjob or inconsistent flag usage in this window.aw_info.jsonsuggests a log-processing or artifact-upload gap (possibly agent jobs failing before the usual artifact upload step) for workflows likeai-moderator,daily-trajectory-grader-implementer, and thesmoke-copilot-*family. This is a log-pipeline/observability gap, not a detection misconfiguration, but worth a follow-up if accurate detection-adoption reporting matters.Smoke Agy (Experimental)— it is the only workflow currently opting out of detection, but at 1 run/7 days it stays well under the >3-runs-in-7-days threshold for flagging, so leave as-is unless its run frequency increases.References:
detectionjob present (default config, not flagged)All reactions