-
Notifications
You must be signed in to change notification settings - Fork 328
[plan] Investigate and fix safe_outputs failures in Smoke Update Cross-Repo PR and Smoke Multi PR #22246
Copy link
Copy link
Closed as not planned
Closed as not planned
Copy link
Labels
Description
Objective
Diagnose and fix the safe_outputs job failures in the Smoke Update Cross-Repo PR and Smoke Multi PR smoke test workflows.
Context
From the Daily Audit Report (discussion #22237):
Two smoke test workflows both failed at the safe_outputs job (not the agent job), suggesting a possible regression in safe-output processing:
| Workflow | Run ID |
|---|---|
| Smoke Update Cross-Repo PR | §23392658504 |
| Smoke Multi PR | §23392726144 |
Both ran close in time and both use the copilot engine. The simultaneous failure of two smoke tests at the same job stage (safe_outputs) suggests a systemic issue rather than an isolated incident.
Investigation Steps
- Use
gh aw audit 23392658504andgh aw audit 23392726144to inspect the failed runs - Check logs for both
safe_outputsjobs to identify the error message/root cause - Check git log around the time of the failures for recent changes to safe-outputs logic
- Look at
actions/setup/js/for any safe-output processing code that may have a bug - If a regression is found, fix it and add a test to prevent recurrence
Files to Investigate
actions/setup/js/— JavaScript safe-output processing scripts.github/workflows/smoke-update-cross-repo-pr.md(or similar).github/workflows/smoke-multi-pr.md(or similar)- Recent commits touching safe-output logic
Acceptance Criteria
- Root cause of
safe_outputsfailures identified - Fix applied (or confirmed as a transient/external failure)
- Both smoke workflows pass on re-run (or regression prevented)
-
make agent-finishpasses
Generated by Plan Command for issue #discussion #22237 · ◷
- expires on Mar 24, 2026, 8:48 AM UTC
Reactions are currently unavailable
Metadata
Metadata
Labels
Type
Fields
Give feedbackNo fields configured for issues without a type.