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