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