Parent Log:
http://ci.aztec-labs.com/3ca30566e9ce997a
Command: 24e90b7895ff1ed6 yarn-project/scripts/run_test.sh stdlib/src/versioning/versioning.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/8cc8a56892d36191eefb49254ebbe49ea99ef4b8
Env: REF_NAME=gh-readonly-queue/next/pr-14921-78d87cb88633aee537d022d6fd8e57ceb74a3a95 CURRENT_VERSION=0.87.6 CI_FULL=1
Date: Wed Jun 18 11:35:00 UTC 2025
System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-14921_amd64_x1-full
Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_71244dbe523bff8b_next
11:35:02 [11:35:02.800]
WARN:
json-rpc:client Failed to fetch from the remote server
11:35:02 err: {
11:35:02 "type": "ComponentsVersionsError",
11:35:02 "message": "Expected component version l1ChainId to be 2 but received 1",
11:35:02 "stack":
11:35:02 ComponentsVersionsError: Expected component version l1ChainId to be 2 but received 1
11:35:02 at Object.onResponse (/home/aztec-dev/aztec-packages/yarn-project/stdlib/src/versioning/versioning.ts:141:17)
11:35:02 at Timeout.sendBatch (/home/aztec-dev/aztec-packages/yarn-project/foundation/dest/json-rpc/client/safe_json_rpc_client.js:69:30)
11:35:02 at processTicksAndRejections (node:internal/process/task_queues:105:5)
11:35:02 "name": "ComponentsVersionsError"
11:35:02 }
11:35:02
PASS src/versioning/versioning.test.ts
11:35:02 versioning
11:35:02 comparing
11:35:02
✓ compresses and checks (2 ms)
11:35:02
✓ throws on mismatch in compressed (14 ms)
11:35:02
✓ validates partial versions
11:35:02
✓ throws on mismatch for partial versions (12 ms)
11:35:02 json-rpc
11:35:02
✓ passes versioning headers (41 ms)
11:35:02
✓ throws on mismatch (13 ms)
11:35:02
✓ passes if missing on server (7 ms)
11:35:02
✓ passes if missing on client (6 ms)
11:35:02
11:35:02
Test Suites: 1 passed, 1 total
11:35:02
Tests: 8 passed, 8 total
11:35:02
Snapshots: 0 total
11:35:02
Time: 0.951 s
11:35:02
Ran all test suites matching stdlib/src/versioning/versioning.test.ts
.
11:35:02
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?