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