Parent Log:
http://ci.aztec-labs.com/29ef878f08dca81b
Command: ef601da20f8e827b yarn-project/scripts/run_test.sh stdlib/src/versioning/versioning.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/d886120f668032e2640beac56487c6f7b18ce81e
Env: REF_NAME=gh-readonly-queue/next/pr-15226-fe574e9be5d341cfa05d23ac296ab738d268f1c0 CURRENT_VERSION=0.87.6 CI_FULL=0
Date: Wed Jun 25 16:20:56 UTC 2025
System: ARCH=arm64 CPUS=64 MEM=247Gi HOSTNAME=pr-15226_arm64_a1-fast
Resources: CPU_LIST=0-63 CPUS=2 MEM=8g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/history_71244dbe523bff8b_next
16:20:58 [16:20:58.390]
WARN:
json-rpc:client Failed to fetch from the remote server
16:20:58 err: {
16:20:58 "type": "ComponentsVersionsError",
16:20:58 "message": "Expected component version l1ChainId to be 2 but received 1",
16:20:58 "stack":
16:20:58 ComponentsVersionsError: Expected component version l1ChainId to be 2 but received 1
16:20:58 at Object.onResponse (/home/aztec-dev/aztec-packages/yarn-project/stdlib/src/versioning/versioning.ts:141:17)
16:20:58 at Timeout.sendBatch (/home/aztec-dev/aztec-packages/yarn-project/foundation/dest/json-rpc/client/safe_json_rpc_client.js:69:30)
16:20:58 at processTicksAndRejections (node:internal/process/task_queues:105:5)
16:20:58 "name": "ComponentsVersionsError"
16:20:58 }
16:20:58
PASS src/versioning/versioning.test.ts
16:20:58 versioning
16:20:58 comparing
16:20:58
✓ compresses and checks (1 ms)
16:20:58
✓ throws on mismatch in compressed (14 ms)
16:20:58
✓ validates partial versions (1 ms)
16:20:58
✓ throws on mismatch for partial versions (1 ms)
16:20:58 json-rpc
16:20:58
✓ passes versioning headers (41 ms)
16:20:58
✓ throws on mismatch (12 ms)
16:20:58
✓ passes if missing on server (6 ms)
16:20:58
✓ passes if missing on client (5 ms)
16:20:58
16:20:58
Test Suites: 1 passed, 1 total
16:20:58
Tests: 8 passed, 8 total
16:20:58
Snapshots: 0 total
16:20:58
Time: 0.654 s
16:20:58
Ran all test suites matching stdlib/src/versioning/versioning.test.ts
.
16:20:58
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?