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