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