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