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