-
Notifications
You must be signed in to change notification settings - Fork 311
Description
Q Workflow Optimization Report — Weekly Run
Issues Found (from live data)
Smoke Update Cross-Repo PR — Persistent Failures
- Run IDs Analyzed: 23296167313, 23368643312, 23380227984, 23344003604, 23324531884, 23274762870, 23245988537
- Failure Rate: 100% of scheduled runs over 7+ days (every 12h)
- Root Cause: The
push-to-pull-request-branchsafe output haslabels: [smoke-test]which requires PR rejig docs #1 ingithubnext/gh-aw-side-repoto have thesmoke-testlabel. That PR does not have this label. - Error from logs:
push_to_pull_request_branch: Pull request is missing required labels: smoke-test. Current labels:(issue [aw] Smoke Update Cross-Repo PR failed #21797) - Pattern: All runs succeed in the agent job, but the
safe_outputsjob's "Process Safe Outputs" step fails consistently.
AI Moderator — DIFC Integrity Filtering (by design, no action needed)
- Runs: 23382312849, 23380925027
- Issue: Cannot read issues with
integrity_tags: ["none:all"]when agent requiresapprovedintegrity - Assessment: Working as designed — the agent correctly reports
missing_datawhen DIFC policy prevents reading low-integrity content. No workflow change needed.
Changes Made
.github/workflows/smoke-update-cross-repo-pr.md
- Removed:
labels: [smoke-test]frompush-to-pull-request-branchconfiguration - Reason: The target PR is already explicitly pinned via
target: "1"intarget-repo: "githubnext/gh-aw-side-repo", making the label constraint redundant and overly restrictive. The label requirement was causing all 7+ scheduled runs to fail.
Expected Improvements
- Resolves 100% failure rate on
smoke-update-cross-repo-prscheduled runs - Every 12h smoke test should resume normal operation
- Eliminates recurring failure issue reports (see [aw] Smoke Update Cross-Repo PR failed #21797)
Validation
✅ smoke-update-cross-repo-pr compiled successfully with strict mode
System Health Summary (7-day window, 100 runs)
| Metric | Value |
|---|---|
| Total runs | 100 |
| Missing tools | 0 |
| Missing data (by design) | 1 (AI Moderator DIFC) |
| Smoke test failures (persistent) | 7+ consecutive |
| Other errors | 0 |
References
- Failure issue: [aw] Smoke Update Cross-Repo PR failed #21797
- Run IDs investigated: 23296167313, 23368643312, 23380227984, 23344003604, 23324531884, 23274762870, 23245988537
- Log analysis:
/tmp/gh-aw/aw-mcp/logs/
Warning
🛡️ Protected Files — Push Permission Denied
This was originally intended as a pull request, but the patch modifies protected files: .github/workflows/smoke-update-cross-repo-pr.md.
The push was rejected because GitHub Actions does not have workflows permission to push these changes, and is never allowed to make such changes, or other authorization being used does not have this permission. A human must create the pull request manually.
To create a pull request with the changes:
# Download the patch from the workflow run
gh run download 23382560681 -n agent -D /tmp/agent-23382560681
# Create a new branch
git checkout -b q/fix-smoke-update-cross-repo-pr-label-constraint-60376e61f51bfe5e main
# Apply the patch (--3way handles cross-repo patches)
git am --3way /tmp/agent-23382560681/aw-q-fix-smoke-update-cross-repo-pr-label-constraint.patch
# Push the branch and create the pull request
git push origin q/fix-smoke-update-cross-repo-pr-label-constraint-60376e61f51bfe5e
gh pr create --title '[q] fix(smoke-update-cross-repo-pr): remove label constraint causing persistent failures (#21797)' --base main --head q/fix-smoke-update-cross-repo-pr-label-constraint-60376e61f51bfe5e --repo github/gh-awNote
🔒 Integrity filtering filtered 2 items
Integrity filtering activated and filtered the following items during workflow execution.
This happens when a tool call accesses a resource that does not meet the required integrity or secrecy level of the workflow.
- resource:get_job_logs (
get_job_logs: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".) - issue:[aw] Smoke Update Cross-Repo PR failed #21797 (
issue_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
- expires on Mar 23, 2026, 3:33 PM UTC