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