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