Parent Log:
http://ci.aztec-labs.com/1923b10caa18faa7
Command: ffd1cbbe745b5db8 yarn-project/scripts/run_test.sh stdlib/src/versioning/versioning.test.ts
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/80d800435dd8dfa325e38593d83b405488449dba
Env: REF_NAME=gh-readonly-queue/next/pr-14444-28bf32bfc2566751e8baa0a9125a9db20d474bee CURRENT_VERSION=0.87.6 CI_FULL=0
Date: Fri Jun 20 16:01:46 UTC 2025
System: ARCH=arm64 CPUS=64 MEM=247Gi HOSTNAME=pr-14444_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:01:47 [16:01:47.888]
WARN:
json-rpc:client Failed to fetch from the remote server
16:01:47 err: {
16:01:47 "type": "ComponentsVersionsError",
16:01:47 "message": "Expected component version l1ChainId to be 2 but received 1",
16:01:47 "stack":
16:01:47 ComponentsVersionsError: Expected component version l1ChainId to be 2 but received 1
16:01:47 at Object.onResponse (/home/aztec-dev/aztec-packages/yarn-project/stdlib/src/versioning/versioning.ts:141:17)
16:01:47 at Timeout.sendBatch (/home/aztec-dev/aztec-packages/yarn-project/foundation/dest/json-rpc/client/safe_json_rpc_client.js:69:30)
16:01:47 at processTicksAndRejections (node:internal/process/task_queues:105:5)
16:01:47 "name": "ComponentsVersionsError"
16:01:47 }
16:01:47
PASS src/versioning/versioning.test.ts
16:01:47 versioning
16:01:47 comparing
16:01:47
✓ compresses and checks (1 ms)
16:01:47
✓ throws on mismatch in compressed (13 ms)
16:01:47
✓ validates partial versions (1 ms)
16:01:47
✓ throws on mismatch for partial versions (1 ms)
16:01:47 json-rpc
16:01:47
✓ passes versioning headers (38 ms)
16:01:47
✓ throws on mismatch (12 ms)
16:01:47
✓ passes if missing on server (6 ms)
16:01:47
✓ passes if missing on client (5 ms)
16:01:47
16:01:47
Test Suites: 1 passed, 1 total
16:01:47
Tests: 8 passed, 8 total
16:01:47
Snapshots: 0 total
16:01:47
Time: 0.629 s
16:01:47
Ran all test suites matching stdlib/src/versioning/versioning.test.ts
.
16:01:47
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?