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