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