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