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