You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Inspected only run 40073428821, job 120815773035, Test Suite, attempt 1, for PR #6313, head 23cedf266b54bd8b3e5e81fb9988711b8acb0e2c. The job API confirms attempt 1; 1 -> 2 is the detector transition. No other attempt was inspected for diagnosis.
This is an aggregate gate, not a test execution job. At 07:36:30 UTC on October 24, Check component results ran with RUST_RESULT=cancelled. Rust build, serial Rust, C#, C++, native SDK, and browser SDK results were all success.
Bash -e passes test "${RUST_BUILD_RESULT}" = success, then exits 1 at test "${RUST_RESULT}" = success. Root cause visible in this exact job: propagation of the cancelled parallel-Rust component, not an independent product-test failure. Cleaning up orphan processes is routine cleanup, not the error. The aggregate log does not explain the cancellation itself; the separately linked upstream incident is diagnosed in #6373 (archive-download timeout in the same attempt).
Suggested updated title:CI flake: Test Suite aggregate fails because RUST_RESULT is cancelled
Duplicate analysis
Searched open and closed issues using RUST_RESULT cancelled, rust-tests-linux, Download Rust test archive, and broad archive/artifact timeout terms; inspected matching Test flakes diagnoses and closed-ticket timelines.
Historical CI flake: Test Suite #6339 has the same gate signature and is closed as a duplicate under the archive-budget tracker; its upstream report CI flake: Test Suite - Rust (3/4) #6338 was consolidated there too. These are history, not separate canonical candidates.
Leaving open:#6330 is not an authorized automatic duplicate-closure target.
Activity
clockwork-labs-bot commentedon Oct 25, 2026
Exact-attempt diagnosis
Inspected only run 40073428821, job 120815773035, Test Suite, attempt 1, for PR #6313, head
23cedf266b54bd8b3e5e81fb9988711b8acb0e2c. The job API confirms attempt 1;1 -> 2is the detector transition. No other attempt was inspected for diagnosis.This is an aggregate gate, not a test execution job. At 07:36:30 UTC on October 24, Check component results ran with
RUST_RESULT=cancelled. Rust build, serial Rust, C#, C++, native SDK, and browser SDK results were allsuccess.Bash
-epassestest "${RUST_BUILD_RESULT}" = success, then exits 1 attest "${RUST_RESULT}" = success. Root cause visible in this exact job: propagation of the cancelled parallel-Rust component, not an independent product-test failure.Cleaning up orphan processesis routine cleanup, not the error. The aggregate log does not explain the cancellation itself; the separately linked upstream incident is diagnosed in #6373 (archive-download timeout in the same attempt).Suggested updated title:
CI flake: Test Suite aggregate fails because RUST_RESULT is cancelledDuplicate analysis
Searched open and closed issues using
RUST_RESULT cancelled,rust-tests-linux,Download Rust test archive, and broad archive/artifact timeout terms; inspected matching Test flakes diagnoses and closed-ticket timelines.Leaving open: #6330 is not an authorized automatic duplicate-closure target.