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 40034002364, job 120692448745, SDK Tests (native 1/2), attempt 1, head 8a8ba6741c8bb06e2a1f26dbf13344b251d21bdd. This is the merge-queue run for PR #6060. The job API confirms attempt 1; attempt 1 -> 2 in the ticket describes the detector transition.
At 22:40:27 UTC on October 23, Extract SDK test support files failed:
Decoding error (36) : Restored data doesn't match checksum
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
Process completed with exit code 2.
The step runs tar --zstd -xf sdk-test-modules.tar.zst followed by tar --zstd -xf "${SDK_TEST_CLIENT_ARCHIVE}" (sdk-test-clients-native.tar.zst) under Bash -e. It does not trace individual command execution, so the log alone cannot distinguish which of these two archives failed. Run SDK test partition was skipped: no SDK tests ran.
Root cause visible here: a zstd support archive failed content-integrity verification during extraction, leaving tar with incomplete input. This is an artifact/setup integrity failure, not a test assertion or compile failure. The common-support and native-client artifact downloads both completed with SHA256 digests matching their advertised values; that does not validate the inner zstd payload. The log does not establish whether the corruption originated during archive creation, local storage/memory handling, or elsewhere. It does not justify blaming an incomplete network download. Routine cleanup and Node deprecation warnings are not the cause.
Suggested updated title:CI flake: SDK support archive extraction fails with zstd checksum mismatch
Duplicate analysis
Searched open and closed public issues, then checked Test flakes membership and existing diagnoses. Searches included Restored data, checksum, decoding, Unexpected EOF, artifact corrupt, tar archive, extraction/artifact terms, and native SDK job names.
Related: CI flake - Truncated Windows build-support artifact #5949, unreadable/truncated Windows build-support archive before smoketests. It has gzip EOF rather than a zstd checksum failure, a different support artifact and platform, and no evidence establishing the same underlying cause.
CI flake: Test Suite #6370 is the downstream aggregate symptom of this same run's native SDK failure, not an older independent root-cause tracker.
Top duplicate candidate: none sufficiently established. Similar tickets exist, but none are close enough to mark this ticket as a duplicate. Leaving open.
Activity
clockwork-labs-bot commentedon Oct 24, 2026
Exact-attempt diagnosis
Inspected only run 40034002364, job 120692448745, SDK Tests (native 1/2), attempt 1, head
8a8ba6741c8bb06e2a1f26dbf13344b251d21bdd. This is the merge-queue run for PR #6060. The job API confirms attempt 1;attempt 1 -> 2in the ticket describes the detector transition.At 22:40:27 UTC on October 23, Extract SDK test support files failed:
The step runs
tar --zstd -xf sdk-test-modules.tar.zstfollowed bytar --zstd -xf "${SDK_TEST_CLIENT_ARCHIVE}"(sdk-test-clients-native.tar.zst) under Bash-e. It does not trace individual command execution, so the log alone cannot distinguish which of these two archives failed. Run SDK test partition was skipped: no SDK tests ran.Root cause visible here: a zstd support archive failed content-integrity verification during extraction, leaving tar with incomplete input. This is an artifact/setup integrity failure, not a test assertion or compile failure. The common-support and native-client artifact downloads both completed with SHA256 digests matching their advertised values; that does not validate the inner zstd payload. The log does not establish whether the corruption originated during archive creation, local storage/memory handling, or elsewhere. It does not justify blaming an incomplete network download. Routine cleanup and Node deprecation warnings are not the cause.
Suggested updated title:
CI flake: SDK support archive extraction fails with zstd checksum mismatchDuplicate analysis
Searched open and closed public issues, then checked Test flakes membership and existing diagnoses. Searches included
Restored data,checksum,decoding,Unexpected EOF,artifact corrupt,tar archive, extraction/artifact terms, and native SDK job names.Top duplicate candidate: none sufficiently established. Similar tickets exist, but none are close enough to mark this ticket as a duplicate. Leaving open.