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