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