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