Parent Log: http://ci.aztec-labs.com/a0f0f050e593860b 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:55 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15095_amd64_x3-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_71244dbe523bff8b_next 10:15:57 [10:15:57.708] WARN: json-rpc:client Failed to fetch from the remote server 10:15:57 err: { 10:15:57 "type": "ComponentsVersionsError", 10:15:57 "message": "Expected component version l1ChainId to be 2 but received 1", 10:15:57 "stack": 10:15:57 ComponentsVersionsError: Expected component version l1ChainId to be 2 but received 1 10:15:57 at Object.onResponse (/home/aztec-dev/aztec-packages/yarn-project/stdlib/src/versioning/versioning.ts:141:17) 10:15:57 at Timeout.sendBatch (/home/aztec-dev/aztec-packages/yarn-project/foundation/dest/json-rpc/client/safe_json_rpc_client.js:69:30) 10:15:57 at processTicksAndRejections (node:internal/process/task_queues:105:5) 10:15:57 "name": "ComponentsVersionsError" 10:15:57 } 10:15:57 PASS src/versioning/versioning.test.ts 10:15:57 versioning 10:15:57 comparing 10:15:57 ✓ compresses and checks (2 ms) 10:15:57 ✓ throws on mismatch in compressed (15 ms) 10:15:57 ✓ validates partial versions 10:15:57 ✓ throws on mismatch for partial versions (5 ms) 10:15:57 json-rpc 10:15:57 ✓ passes versioning headers (47 ms) 10:15:57 ✓ throws on mismatch (17 ms) 10:15:57 ✓ passes if missing on server (10 ms) 10:15:57 ✓ passes if missing on client (16 ms) 10:15:57 10:15:57 Test Suites: 1 passed, 1 total 10:15:57 Tests: 8 passed, 8 total 10:15:57 Snapshots: 0 total 10:15:57 Time: 1.027 s 10:15:57 Ran all test suites matching stdlib/src/versioning/versioning.test.ts. 10:15:57 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?