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