Parent Log: http://ci.aztec-labs.com/23bd615181153a40 Command: 2b73ae8ee702d4cd yarn-project/scripts/run_test.sh stdlib/src/versioning/versioning.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/78a5deb1c3aa24503935bbda20f9374ba35aa5c4 Env: REF_NAME=gh-readonly-queue/next/pr-15112-f17855f94a58189a98dd378743e67b774ea38144 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Wed Jun 18 10:13:32 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15112_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:13:34 [10:13:34.928] WARN: json-rpc:client Failed to fetch from the remote server 10:13:34 err: { 10:13:34 "type": "ComponentsVersionsError", 10:13:34 "message": "Expected component version l1ChainId to be 2 but received 1", 10:13:34 "stack": 10:13:34 ComponentsVersionsError: Expected component version l1ChainId to be 2 but received 1 10:13:34 at Object.onResponse (/home/aztec-dev/aztec-packages/yarn-project/stdlib/src/versioning/versioning.ts:141:17) 10:13:34 at Timeout.sendBatch (/home/aztec-dev/aztec-packages/yarn-project/foundation/dest/json-rpc/client/safe_json_rpc_client.js:69:30) 10:13:34 at processTicksAndRejections (node:internal/process/task_queues:105:5) 10:13:34 "name": "ComponentsVersionsError" 10:13:34 } 10:13:34 PASS src/versioning/versioning.test.ts 10:13:34 versioning 10:13:34 comparing 10:13:34 compresses and checks (1 ms) 10:13:34 throws on mismatch in compressed (32 ms) 10:13:34 validates partial versions (1 ms) 10:13:34 throws on mismatch for partial versions (1 ms) 10:13:34 json-rpc 10:13:34 passes versioning headers (52 ms) 10:13:34 throws on mismatch (22 ms) 10:13:34 passes if missing on server (16 ms) 10:13:34 passes if missing on client (6 ms) 10:13:34 10:13:34 Test Suites: 1 passed, 1 total 10:13:34 Tests: 8 passed, 8 total 10:13:34 Snapshots: 0 total 10:13:34 Time: 0.954 s 10:13:34 Ran all test suites matching stdlib/src/versioning/versioning.test.ts. 10:13:34 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?