Parent Log: http://ci.aztec-labs.com/b19cd8e5b38225d7 Command: f1d5df06d37e0c0f yarn-project/scripts/run_test.sh stdlib/src/versioning/versioning.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/5c77169d7f01a9e15bc19b05fa231fd96111d7dd Env: REF_NAME=gh-readonly-queue/next/pr-15042-d5c48d855d83e19712c6b72281801c6fce176ec1 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Wed Jun 18 15:02:12 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15042_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:02:14 [15:02:14.840] WARN: json-rpc:client Failed to fetch from the remote server 15:02:14 err: { 15:02:14 "type": "ComponentsVersionsError", 15:02:14 "message": "Expected component version l1ChainId to be 2 but received 1", 15:02:14 "stack": 15:02:14 ComponentsVersionsError: Expected component version l1ChainId to be 2 but received 1 15:02:14 at Object.onResponse (/home/aztec-dev/aztec-packages/yarn-project/stdlib/src/versioning/versioning.ts:141:17) 15:02:14 at Timeout.sendBatch (/home/aztec-dev/aztec-packages/yarn-project/foundation/dest/json-rpc/client/safe_json_rpc_client.js:69:30) 15:02:14 at processTicksAndRejections (node:internal/process/task_queues:105:5) 15:02:14 "name": "ComponentsVersionsError" 15:02:14 } 15:02:14 PASS src/versioning/versioning.test.ts 15:02:14 versioning 15:02:14 comparing 15:02:14 compresses and checks (2 ms) 15:02:14 throws on mismatch in compressed (17 ms) 15:02:14 validates partial versions (1 ms) 15:02:14 throws on mismatch for partial versions (2 ms) 15:02:14 json-rpc 15:02:14 passes versioning headers (65 ms) 15:02:14 throws on mismatch (16 ms) 15:02:14 passes if missing on server (9 ms) 15:02:14 passes if missing on client (16 ms) 15:02:14 15:02:14 Test Suites: 1 passed, 1 total 15:02:14 Tests: 8 passed, 8 total 15:02:14 Snapshots: 0 total 15:02:14 Time: 0.969 s 15:02:14 Ran all test suites matching stdlib/src/versioning/versioning.test.ts. 15:02:14 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?