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