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