Skip to content

add option to use libbacktrace for backtraces in crash reports #10985

add option to use libbacktrace for backtraces in crash reports

add option to use libbacktrace for backtraces in crash reports #10985

Triggered via pull request January 29, 2026 20:46
Status Failure
Total duration 22m 20s
Artifacts

ci.yml

on: pull_request
test-ubuntu-latest
14s
test-ubuntu-latest
test-ubuntu-latest-cmake-tls
19m 26s
test-ubuntu-latest-cmake-tls
test-sanitizer-address
16s
test-sanitizer-address
test-rdma
5s
test-rdma
build-debian-old
12s
build-debian-old
build-macos-latest
16s
build-macos-latest
build-32bit
2m 43s
build-32bit
build-libc-malloc
17s
build-libc-malloc
build-almalinux8-jemalloc
21s
build-almalinux8-jemalloc
format-yaml
21s
format-yaml
Matrix: test-ubuntu-latest-compatibility
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 2 warnings
build-macos-latest
Process completed with exit code 1.
test-ubuntu-latest-compatibility (8.0.6, valkey-8.0.6-noble-x86_64.tar.gz)
Process completed with exit code 100.
test-sanitizer-address
Process completed with exit code 100.
test-rdma
Process completed with exit code 100.
build-debian-old
Process completed with exit code 100.
test-ubuntu-latest-compatibility (8.1.4, valkey-8.1.4-noble-x86_64.tar.gz)
Process completed with exit code 100.
test-ubuntu-latest-compatibility (7.2.11, valkey-7.2.11-noble-x86_64.tar.gz)
Process completed with exit code 100.
build-almalinux8-jemalloc
Process completed with exit code 1.
test-ubuntu-latest
Process completed with exit code 100.
build-libc-malloc
Process completed with exit code 100.
build-macos-latest
No available formula with the name "libbacktrace". Did you mean libkate?
format-yaml
Restore cache failed: Dependencies file is not found in /home/runner/work/valkey/valkey. Supported file pattern: go.sum