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