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