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