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