Skip to content

[CI Failure Doctor] CI Failure Investigation - Run #35122 #15185

@github-actions

Description

@github-actions

🏥 CI Failure Investigation - Run #35122

Summary

  • The Integration: Workflow Safe Outputs integration suite passed its Go tests but the workflow failed while finalizing the artifact upload, because the Azure blob storage connection was reset before the artifact could finish uploading.

Failure Details

Root Cause Analysis

actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 tried to finalize test-result-integration-Workflow Safe Outputs after the Go tests completed, but the Azure request failed with ECONNRESET before the artifact could be finalized, so the job terminated with Failed to FinalizeArtifact despite every test passing.

Failed Jobs and Errors

  • Integration: Workflow Safe Outputsactions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 finalizing test-result-integration-Workflow Safe Outputs failed with Failed to FinalizeArtifact: Unable to make request: ECONNRESET.

Investigation Findings

  • The Go integration tests succeed (ok github.com/github/gh-aw/pkg/workflow 0.311s), proving the code logic is healthy and the failure is infrastructure-related.
  • The failure occurs during the artifact upload finalization, which means downstream consumers never see the test-result JSON even though it was created.
  • Downstream jobs that rely on these artifacts (coverage comparisons, canaries, etc.) will fail once the artifact is missing, so we must ensure the upload step reliably finishes before they run.

Recommended Actions

  • Re-run the workflow so that the artifact upload can finish successfully; ECONNRESET is typically a transient network issue.
  • If this keeps recurring, add retry logic or a wrapper around the upload-artifact step so that temporary Azure connection resets don’t permanently fail the job.

Prevention Strategies

  • Detect and surface artifact upload failures earlier so downstream jobs clearly know when their inputs were never produced rather than guessing about missing tests.
  • Introduce retries or do a sanity check after every upload-artifact step that is critical for coverage/comparison jobs, especially when exposing the artifact to other stages.

AI Team Self-Improvement

When monitoring workflow failures, treat actions/upload-artifact finalization errors (e.g., Failed to FinalizeArtifact: Unable to make request: ECONNRESET) as infrastructure issues and either rerun the job or instruct downstream agents to add retries instead of assuming failing tests.

Historical Context

Issue #14811 (Run #34708) also recorded a finalization failure, though that one saw 403 Forbidden. This ECONNRESET is a new delivery error but affects the same artifact upload path.

AI generated by CI Failure Doctor

To add this workflow in your repository, run gh aw add githubnext/agentics/workflows/ci-doctor.md@ea350161ad5dcc9624cf510f134c6a9e39a6f94d. See usage guide.

  • expires on Feb 13, 2026, 3:22 PM UTC

Metadata

Metadata

Assignees

No one assigned

    Labels

    cookieIssue Monster Loves Cookies!

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions