Skip to content

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

use rdb to startAppendonly after primary-replica full sync

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

Triggered via push March 25, 2025 06:01
Status Failure
Total duration 30m 57s
Artifacts

ci.yml

on: push
test-ubuntu-latest
28m 17s
test-ubuntu-latest
test-ubuntu-latest-cmake
28m 13s
test-ubuntu-latest-cmake
test-sanitizer-address
30m 45s
test-sanitizer-address
test-rdma
2m 59s
test-rdma
build-debian-old
1m 34s
build-debian-old
build-macos-latest
29s
build-macos-latest
build-32bit
2m 7s
build-32bit
build-libc-malloc
49s
build-libc-malloc
build-almalinux8-jemalloc
1m 44s
build-almalinux8-jemalloc
format-yaml
17s
format-yaml
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 1 warning
test-ubuntu-latest-cmake
Process completed with exit code 1.
test-ubuntu-latest
Process completed with exit code 1.
test-sanitizer-address
Process completed with exit code 1.
format-yaml
Restore cache failed: Dependencies file is not found in /home/runner/work/valkey/valkey. Supported file pattern: go.sum