Skip to content

Use Backtrace::capture instead of force_capture #18534

Use Backtrace::capture instead of force_capture

Use Backtrace::capture instead of force_capture #18534

Triggered via pull request February 20, 2026 14:22
Status Failure
Total duration 31m 30s
Artifacts

build_and_test.yml

on: pull_request
fuzzers-preflight
7s
fuzzers-preflight
qemu-changes
6s
qemu-changes
Matrix: common
Matrix: utils
Matrix: 🚀 full_system/unicorn
Matrix: fuzzers
Matrix: qemu-system-i386
Matrix: qemu-system
Matrix: qemu-user
🔧 libafl_qemu_asan
0s
🔧 libafl_qemu_asan
Matrix: windows
Matrix: ubuntu-check
Fit to window
Zoom out
Zoom in

Annotations

9 errors and 3 warnings
cargo-fmt
Process completed with exit code 1.
🚀 binary_only/frida_crash_repro
Process completed with exit code 1.
ubuntu-doc-test
Process completed with exit code 101.
python-bindings
Process completed with exit code 1.
🚀 structure_aware/libfuzzer_stb_image_concolic
Process completed with exit code 1.
ubuntu
Process completed with exit code 101.
macos
Process completed with exit code 101.
🚀 full_system/nyx_libxml2_parallel
Process completed with exit code 1.
🚀 full_system/nyx_libxml2_standalone
Process completed with exit code 1.
common (macOS-latest)
llvm@18 18.1.8 is already installed and up-to-date. To reinstall 18.1.8, run: brew reinstall llvm@18
macos
llvm@18 18.1.8 is already installed and up-to-date. To reinstall 18.1.8, run: brew reinstall llvm@18
macos
python@3.14 3.14.3_1 is already installed and up-to-date. To reinstall 3.14.3_1, run: brew reinstall python@3.14