Skip to content

[deep-report] Pre-bundle the Process Safe Outputs step stdout/stderr on safe-output job failure #47606

Description

@github-actions

Description

When a safe_outputs job fails at the Process Safe Outputs step, its stdout/stderr are not included in the pre-bundled run artifacts, and the logs CLI times out at 300s. As a result, every in-scope safe-output failure (both 2026-07-23 failures and the 07-20 pair) can only be family-attributed, never root-caused. This is now the 5th+ class of unreadable JOB-layer failure and is the single most important cross-cutting observability gap — it blocks confirmation of the review-422 and scheduled-target-resolution fixes.

Expected Impact

Unblocks root-cause analysis for every safe-output job failure. Auditors can read the exact error instead of inferring from item-type + trigger context.

Suggested Agent

Copilot SWE Agent or Agentic Maintenance.

Estimated Effort

Medium (1-4 hours) — upload the step stdout/stderr as a run artifact on safe_outputs job failure.

Data Source

DeepReport Intelligence analysis 2026-07-23; Safe Output Health report #47473 (Work Item 1, High).

Generated by 🔬 Deep Report · age00 · 242.8 AIC · ⌖ 11.4 AIC · ⊞ 10.3K · ◷

  • expires on Jul 25, 2026, 7:32 AM UTC-08:00

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions