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