Parent Log:
http://ci.aztec-labs.com/5dedeee27fb005f9
Command: 1f475c5d66a44412 yarn-project/scripts/run_test.sh stdlib/src/versioning/versioning.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/e56baa7f24bac54baf9e2f22f6f33ae6fa8b8c0f
Env: REF_NAME=gh-readonly-queue/next/pr-14891-76ca48a2187e3506bb464eae574e49476c2876ca CURRENT_VERSION=0.87.6 CI_FULL=0
Date: Fri Jun 13 19:23:06 UTC 2025
System: ARCH=arm64 CPUS=64 MEM=247Gi HOSTNAME=pr-14891_arm64_a1-fast
Resources: CPU_LIST=0-63 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_71244dbe523bff8b_next
19:23:07 [19:23:07.757]
WARN:
json-rpc:client Failed to fetch from the remote server
19:23:07 err: {
19:23:07 "type": "ComponentsVersionsError",
19:23:07 "message": "Expected component version l1ChainId to be 2 but received 1",
19:23:07 "stack":
19:23:07 ComponentsVersionsError: Expected component version l1ChainId to be 2 but received 1
19:23:07 at Object.onResponse (/home/aztec-dev/aztec-packages/yarn-project/stdlib/src/versioning/versioning.ts:141:17)
19:23:07 at Timeout.sendBatch (/home/aztec-dev/aztec-packages/yarn-project/foundation/dest/json-rpc/client/safe_json_rpc_client.js:69:30)
19:23:07 at processTicksAndRejections (node:internal/process/task_queues:105:5)
19:23:07 "name": "ComponentsVersionsError"
19:23:07 }
19:23:07
PASS src/versioning/versioning.test.ts
19:23:07 versioning
19:23:07 comparing
19:23:07
✓ compresses and checks (1 ms)
19:23:07
✓ throws on mismatch in compressed (10 ms)
19:23:07
✓ validates partial versions (1 ms)
19:23:07
✓ throws on mismatch for partial versions (1 ms)
19:23:07 json-rpc
19:23:07
✓ passes versioning headers (40 ms)
19:23:07
✓ throws on mismatch (13 ms)
19:23:07
✓ passes if missing on server (7 ms)
19:23:07
✓ passes if missing on client (5 ms)
19:23:07
19:23:07
Test Suites: 1 passed, 1 total
19:23:07
Tests: 8 passed, 8 total
19:23:07
Snapshots: 0 total
19:23:07
Time: 0.65 s
19:23:07
Ran all test suites matching /stdlib\/src\/versioning\/versioning.test.ts/i
.
19:23:07
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?