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