phantom/bitcoin
1
0
Fork 0
mirror of https://github.com/bitcoin/bitcoin.git synced 2025-04-29 14:59:39 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

Merge bitcoin/bitcoin#32245: doc: Updates how to reproduce fuzz CI failure locally
Some checks failed
CI / test each commit (push) Has been cancelled
Details
CI / macOS 14 native, arm64, no depends, sqlite only, gui (push) Has been cancelled
Details
CI / macOS 14 native, arm64, fuzz (push) Has been cancelled
Details
CI / Windows native, VS 2022 (push) Has been cancelled
Details
CI / Windows native, fuzz, VS 2022 (push) Has been cancelled
Details
CI / Linux->Windows cross, no tests (push) Has been cancelled
Details
CI / ASan + LSan + UBSan + integer, no depends, USDT (push) Has been cancelled
Details
CI / Windows, test cross-built (push) Has been cancelled
Details

Browse source 
8fe001d597 doc: Updates how to reproduce fuzz CI failure locally (Sergi Delgado Segura)

Pull request description:

  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.

ACKs for top commit:
  maflcko:
    lgtm ACK 8fe001d597
  glozow:
    ACK 8fe001d597

Tree-SHA512: 7436d71a30bbbffc34770027f1deeacca2de528d8d1b333431d6070c2ba779ecfcdaf25dc791d2154ba4dd37824d06aed2695a8412d7ca1f29e5bd1796d42aeb
This commit is contained in:
merge-script 2025-04-11 16:34:41 -04:00
commit 817edfb21e
No known key found for this signature in database
GPG key ID: BA03F4DBE0C63FB4
1 changed files with 7 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
doc/fuzzing.md
View file

@ -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: - run the fuzzer with the case number appended to the seed corpus path:
`FUZZ=process_message build_fuzz/bin/fuzz `FUZZ=process_message build_fuzz/bin/fuzz
qa-assets/fuzz_corpora/process_message/1bc91feec9fc00b107d97dc225a9f2cdaa078eb6` 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 ## Submit improved coverage