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