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