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