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