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