Parent Log: http://ci.aztec-labs.com/c9b88c5eb30a270d Command: f2016651899c5161 yarn-project/scripts/run_test.sh stdlib/src/versioning/versioning.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/832c9f298cdc0c0098b9ffb3f9e8b69de37f2b14 Env: REF_NAME=gh-readonly-queue/next/pr-15169-227fd751f8d3e07a96e4c1564665f0676f8222af CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Mon Jun 23 12:04:50 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15169_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:04:52 [12:04:52.055] WARN: json-rpc:client Failed to fetch from the remote server 12:04:52 err: { 12:04:52 "type": "ComponentsVersionsError", 12:04:52 "message": "Expected component version l1ChainId to be 2 but received 1", 12:04:52 "stack": 12:04:52 ComponentsVersionsError: Expected component version l1ChainId to be 2 but received 1 12:04:52 at Object.onResponse (/home/aztec-dev/aztec-packages/yarn-project/stdlib/src/versioning/versioning.ts:141:17) 12:04:52 at Timeout.sendBatch (/home/aztec-dev/aztec-packages/yarn-project/foundation/dest/json-rpc/client/safe_json_rpc_client.js:69:30) 12:04:52 at processTicksAndRejections (node:internal/process/task_queues:105:5) 12:04:52 "name": "ComponentsVersionsError" 12:04:52 } 12:04:52 PASS src/versioning/versioning.test.ts 12:04:52 versioning 12:04:52 comparing 12:04:52 ✓ compresses and checks (2 ms) 12:04:52 ✓ throws on mismatch in compressed (21 ms) 12:04:52 ✓ validates partial versions 12:04:52 ✓ throws on mismatch for partial versions (1 ms) 12:04:52 json-rpc 12:04:52 ✓ passes versioning headers (55 ms) 12:04:52 ✓ throws on mismatch (13 ms) 12:04:52 ✓ passes if missing on server (9 ms) 12:04:52 ✓ passes if missing on client (6 ms) 12:04:52 12:04:52 Test Suites: 1 passed, 1 total 12:04:52 Tests: 8 passed, 8 total 12:04:52 Snapshots: 0 total 12:04:52 Time: 0.815 s 12:04:52 Ran all test suites matching stdlib/src/versioning/versioning.test.ts. 12:04:52 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?