Skip to content

use rdb to startAppendonly after primary-replica full sync #6

use rdb to startAppendonly after primary-replica full sync

use rdb to startAppendonly after primary-replica full sync #6

Triggered via push March 31, 2025 03:12
Status Cancelled
Total duration 8m 27s
Artifacts

ci.yml

on: push
test-ubuntu-latest
7m 56s
test-ubuntu-latest
test-ubuntu-latest-cmake
7m 58s
test-ubuntu-latest-cmake
test-sanitizer-address
7m 57s
test-sanitizer-address
test-rdma
3m 1s
test-rdma
build-debian-old
1m 33s
build-debian-old
build-macos-latest
37s
build-macos-latest
build-32bit
1m 59s
build-32bit
build-libc-malloc
58s
build-libc-malloc
build-almalinux8-jemalloc
1m 42s
build-almalinux8-jemalloc
format-yaml
19s
format-yaml
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 1 warning
test-ubuntu-latest-cmake
Canceling since a higher priority waiting request for 'ci-refs/heads/use-rdb-start-appendonly' exists
test-ubuntu-latest-cmake
The operation was canceled.
test-ubuntu-latest
Canceling since a higher priority waiting request for 'ci-refs/heads/use-rdb-start-appendonly' exists
test-ubuntu-latest
The operation was canceled.
test-sanitizer-address
Canceling since a higher priority waiting request for 'ci-refs/heads/use-rdb-start-appendonly' exists
test-sanitizer-address
The operation was canceled.
format-yaml
Restore cache failed: Dependencies file is not found in /home/runner/work/valkey/valkey. Supported file pattern: go.sum