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