Parent Log: http://ci.aztec-labs.com/24c394738399f7e2 Command: 246560b53abce7e6 yarn-project/scripts/run_test.sh stdlib/src/versioning/versioning.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/69efc9daf98e823f486416900de52fe8a44f25d9 Env: REF_NAME=gh-readonly-queue/next/pr-15187-6e2f55a89973b55c8c3c210b7f3a692b4d3d6473 CURRENT_VERSION=0.87.6 CI_FULL=0 Date: Mon Jun 23 16:12:59 UTC 2025 System: ARCH=arm64 CPUS=64 MEM=247Gi HOSTNAME=pr-15187_arm64_a1-fast Resources: CPU_LIST=0-63 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_71244dbe523bff8b_next 16:13:00 [16:13:00.525] WARN: json-rpc:client Failed to fetch from the remote server 16:13:00 err: { 16:13:00 "type": "ComponentsVersionsError", 16:13:00 "message": "Expected component version l1ChainId to be 2 but received 1", 16:13:00 "stack": 16:13:00 ComponentsVersionsError: Expected component version l1ChainId to be 2 but received 1 16:13:00 at Object.onResponse (/home/aztec-dev/aztec-packages/yarn-project/stdlib/src/versioning/versioning.ts:141:17) 16:13:00 at Timeout.sendBatch (/home/aztec-dev/aztec-packages/yarn-project/foundation/dest/json-rpc/client/safe_json_rpc_client.js:69:30) 16:13:00 at processTicksAndRejections (node:internal/process/task_queues:105:5) 16:13:00 "name": "ComponentsVersionsError" 16:13:00 } 16:13:00 PASS src/versioning/versioning.test.ts 16:13:00 versioning 16:13:00 comparing 16:13:00 ✓ compresses and checks (1 ms) 16:13:00 ✓ throws on mismatch in compressed (13 ms) 16:13:00 ✓ validates partial versions 16:13:00 ✓ throws on mismatch for partial versions (1 ms) 16:13:00 json-rpc 16:13:00 ✓ passes versioning headers (39 ms) 16:13:00 ✓ throws on mismatch (12 ms) 16:13:00 ✓ passes if missing on server (7 ms) 16:13:00 ✓ passes if missing on client (6 ms) 16:13:00 16:13:00 Test Suites: 1 passed, 1 total 16:13:00 Tests: 8 passed, 8 total 16:13:00 Snapshots: 0 total 16:13:00 Time: 0.638 s 16:13:00 Ran all test suites matching stdlib/src/versioning/versioning.test.ts. 16:13:00 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?