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