Skip to content

CI flake: Test Suite - Rust (3/4) #6618

Closed as duplicate
Closed as duplicate

Description

@clockwork-labs-bot

Detected by CI Gremlin after a failed GitHub Actions attempt succeeded on rerun.

Tests:

  • Test Suite - Rust (3/4)

Error:
The job has exceeded the maximum execution time of 10m0s

Failed job runs:

Timeout detection:

  • Source: check-run annotation
  • Inferred: no
  • Detail: The job has exceeded the maximum execution time of 10m0s

Context:

  • none

Activity

  1. clockwork-labs-bot commented on Nov 17, 2026

    @clockwork-labs-bot
    ContributorAuthor

    Symptoms and root cause

    Exact failed Rust shard job: run 44078291964, job 134070533410, attempt 2. Download Rust test archive spent 9m53s handling the 5,555,285,561-byte rust-tests-linux artifact, until the check-run annotation reported The job has exceeded the maximum execution time of 10m0s. Download started at 13:24:24 UTC; no completion message appeared before cancellation at 13:34:16. Run Rust test partition was skipped. The transfer/handling exhausted the shared job budget; the logs do not distinguish a network stall, storage/extraction bottleneck, or other artifact-action slowdown. This is a genuine timeout, not cancellation-only. Attempt 3, job 134131580581, downloaded the same artifact and passed 424/424 tests.

    Duplicate selection

    Searched all 106 open Test flakes project issues across repositories, plus organization-wide open archive/artifact/timeout/job-budget searches. Selected #6330: the same specific symptom—Rust archive transfer/handling consumes the shard job budget, before tests start. Its established consolidation and 44 distinct incoming canonical duplicate sources (before this invocation) support it as the root. Artifact listing connection reset (#6535), checksum mismatch (#6369), truncated build-support artifact (#5949), and every-component-skipped aggregate (#5930) have different diagnostics absent here. Only open candidate tickets were investigated; no existing/root ticket was modified.

    Proposed operations

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions