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