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