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