Skip to content

use rdb to start appendonly after primary-replica full sync #4

use rdb to start appendonly after primary-replica full sync

use rdb to start appendonly after primary-replica full sync #4

Triggered via push March 30, 2025 18:41
Status Failure
Total duration 1m 29s
Artifacts

ci.yml

on: push
test-ubuntu-latest
43s
test-ubuntu-latest
test-ubuntu-latest-cmake
1m 19s
test-ubuntu-latest-cmake
test-sanitizer-address
22s
test-sanitizer-address
test-rdma
1m 21s
test-rdma
build-debian-old
53s
build-debian-old
build-macos-latest
13s
build-macos-latest
build-32bit
54s
build-32bit
build-libc-malloc
16s
build-libc-malloc
build-almalinux8-jemalloc
55s
build-almalinux8-jemalloc
format-yaml
18s
format-yaml
Fit to window
Zoom out
Zoom in

Annotations

9 errors and 1 warning
build-macos-latest
Process completed with exit code 2.
build-libc-malloc
Process completed with exit code 2.
test-sanitizer-address
Process completed with exit code 2.
test-ubuntu-latest
Process completed with exit code 2.
build-debian-old
Process completed with exit code 2.
build-32bit
Process completed with exit code 2.
build-almalinux8-jemalloc
Process completed with exit code 2.
test-ubuntu-latest-cmake
Process completed with exit code 2.
test-rdma
Process completed with exit code 2.
format-yaml
Restore cache failed: Dependencies file is not found in /home/runner/work/valkey/valkey. Supported file pattern: go.sum