Skip to content
CI

Introducing version vector to solve GC problem #2531

Sign in to view logs

Introducing version vector to solve GC problem

Introducing version vector to solve GC problem #2531

Triggered via pull request September 9, 2024 09:31
@JOOHOJANGJOOHOJANG
synchronize #899
hybrid-clock-version-vector-modified
Status Failure
Total duration 1m 0s
Artifacts –

ci.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 2 warnings
build (18.x): packages/sdk/test/bench/document.bench.ts#L2
'MaxTimeTicket' is defined but never used
build (18.x): packages/sdk/test/bench/text.bench.ts#L2
'MaxTimeTicket' is defined but never used
build (18.x): packages/sdk/test/bench/tree.bench.ts#L2
'MaxTimeTicket' is defined but never used
build (18.x)
Process completed with exit code 1.
build (18.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (18.x)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, pnpm/action-setup@v2, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/