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