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