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