Parent Log: http://ci.aztec-labs.com/3b0d30f42ff50ca8 Command: 95671b91d9414288 yarn-project/scripts/run_test.sh stdlib/src/versioning/versioning.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/347f29fb98cc855ead57129b4d1a444d9fb16820 Env: REF_NAME=gh-readonly-queue/next/pr-15059-16fc84676c7308fa5f7ca4a54b67319803d0f5b7 CURRENT_VERSION=0.87.6 CI_FULL=0 Date: Mon Jun 16 16:03:21 UTC 2025 System: ARCH=arm64 CPUS=64 MEM=247Gi HOSTNAME=pr-15059_arm64_a1-fast Resources: CPU_LIST=0-63 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_71244dbe523bff8b_next 16:03:23 [16:03:23.265] WARN: json-rpc:client Failed to fetch from the remote server 16:03:23 err: { 16:03:23 "type": "ComponentsVersionsError", 16:03:23 "message": "Expected component version l1ChainId to be 2 but received 1", 16:03:23 "stack": 16:03:23 ComponentsVersionsError: Expected component version l1ChainId to be 2 but received 1 16:03:23 at Object.onResponse (/home/aztec-dev/aztec-packages/yarn-project/stdlib/src/versioning/versioning.ts:141:17) 16:03:23 at Timeout.sendBatch (/home/aztec-dev/aztec-packages/yarn-project/foundation/dest/json-rpc/client/safe_json_rpc_client.js:69:30) 16:03:23 at processTicksAndRejections (node:internal/process/task_queues:105:5) 16:03:23 "name": "ComponentsVersionsError" 16:03:23 } 16:03:23 PASS src/versioning/versioning.test.ts 16:03:23 versioning 16:03:23 comparing 16:03:23 ✓ compresses and checks (1 ms) 16:03:23 ✓ throws on mismatch in compressed (10 ms) 16:03:23 ✓ validates partial versions (1 ms) 16:03:23 ✓ throws on mismatch for partial versions (1 ms) 16:03:23 json-rpc 16:03:23 ✓ passes versioning headers (40 ms) 16:03:23 ✓ throws on mismatch (12 ms) 16:03:23 ✓ passes if missing on server (7 ms) 16:03:23 ✓ passes if missing on client (4 ms) 16:03:23 16:03:23 Test Suites: 1 passed, 1 total 16:03:23 Tests: 8 passed, 8 total 16:03:23 Snapshots: 0 total 16:03:23 Time: 0.675 s 16:03:23 Ran all test suites matching stdlib/src/versioning/versioning.test.ts. 16:03:23 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?