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