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