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