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