Skip to content

CI flake: Test Suite - Rust Serial & Features #6631

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 Serial & Features

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 18, 2026

    @clockwork-labs-bot
    ContributorAuthor

    Symptoms and root cause

    Exact serial job 135035302674, run 44360512451, attempt 1: feature tests pass 9/9 + 3/3. Downloading/handling the 5,637,931,946-byte Rust test archive takes 5m11s (18:44:06–18:49:17 UTC), with matching digest and successful completion. Nextest extracts its contents in 36.80s; all 48/48 serial tests pass in 139.858s, ending 18:52:29.946 UTC. About 170ms later, the operation is cancelled and the serial step is recorded cancelled. The exact check annotation confirms The job has exceeded the maximum execution time of 10m0s.

    This is shared job-budget exhaustion after slow archive handling, despite all tests passing—not an assertion failure, test hang, or cancellation-only incident. The log does not establish the transfer/storage bottleneck or why final process completion missed the cutoff. Exact attempt-2 serial job 135175846865 handles the same archive/digest in 64s, passes 9 + 3 + 48 tests (serial tests 151.133s), and succeeds; the tests themselves were not faster on retry.

    Exact attempt-2 aggregate job 135179971581 succeeds.

    Duplicate selection

    Searched all 107 OPEN Test flakes project issues across repositories, plus organization-wide OPEN archive and timeout diagnostics. Selected freshly OPEN #6330, with 49 distinct incoming canonical duplicate sources before this invocation. The root explicitly human-consolidates both archive handling that prevents tests starting and ~6-minute transfers that leave insufficient serial-test budget. This attempt is the latter boundary case: all tests pass, but job completion misses the remaining budget. No long post-cleanup silence or independently stalled finalization is present; the shared budget is consumed by setup, archive handling and serial execution. The matching checksum excludes a checksum-mismatch signature; there is no artifact-listing reset or all-components-skipped wrapper. No closed candidate tickets were searched or inspected.

    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