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