From 8fe001d59722800417334a09142c559887b54b28 Mon Sep 17 00:00:00 2001 From: Sergi Delgado Segura Date: Thu, 10 Apr 2025 10:16:45 -0400 Subject: [PATCH] doc: Updates how to reproduce fuzz CI failure locally The current version of the doc does not explain how to reproduce a recent fuzzing CI failure (not yet part of the corpora). Add instructions on how to manually create a crash file based on a report. --- doc/fuzzing.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/doc/fuzzing.md b/doc/fuzzing.md index 816eee53f90..c3b13a7f1ff 100644 --- a/doc/fuzzing.md +++ b/doc/fuzzing.md @@ -136,6 +136,13 @@ Patience is useful; even with improved throughput, libFuzzer may need days and - run the fuzzer with the case number appended to the seed corpus path: `FUZZ=process_message build_fuzz/bin/fuzz qa-assets/fuzz_corpora/process_message/1bc91feec9fc00b107d97dc225a9f2cdaa078eb6` +- If the file does not exist, make sure you are checking out the exact same commit id + for the qa-assets repo. If the file was found while running the fuzz engine in the CI, + you should be able to reproduce the crash locally with the same (or a similar input) + within a few minutes. Alternatively, you can use the base64 encoded file from the CI log, + if it exists. e.g. + `echo "Nb6Fc/97AACAAAD/ewAAgAAAAIAAAACAAAAAoA==" | + base64 --decode > qa-assets/fuzz_corpora/process_message/1bc91feec9fc00b107d97dc225a9f2cdaa078eb6` ## Submit improved coverage