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