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