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