diff options
author | MarcoFalke <falke.marco@gmail.com> | 2020-05-16 06:14:42 -0400 |
---|---|---|
committer | MarcoFalke <falke.marco@gmail.com> | 2020-05-16 06:14:45 -0400 |
commit | 5a454d78825f7ff7efaa52eddf8eb1503931b64f (patch) | |
tree | 6393235364cb8dd040ee3c41e2ef251c214a50be /test | |
parent | 951870807ea28e05cf074e364e1b55e985ab9f6d (diff) | |
parent | 8d306862ef077f2a71931372dd6a2efa05188c84 (diff) | |
download | bitcoin-5a454d78825f7ff7efaa52eddf8eb1503931b64f.tar.xz |
Merge #18634: ci: Add fuzzbuzz integration configuration file
8d306862ef077f2a71931372dd6a2efa05188c84 ci: Add fuzzbuzz integration (practicalswift)
Pull request description:
Add fuzzbuzz integration.
Just like #15338 enabled optional FreeBSD building via Cirrus CI (`.cirrus.yml`) this PR adds optional fuzzing via fuzzbuzz (`.fuzzbuzz.yml`).
Having this merged makes is easier for people to fuzz Bitcoin Core (via their forked repos) using their fuzzbuzz account and then hopefully submit coverage increasing corpus additions upstreams to to https://github.com/bitcoin-core/qa-assets.
Historically it has been mostly been me and MarcoFalke who submit test cases to `qa-assets`, but with this change hopefully more people will join the hunt for coverage increasing fuzzing inputs :)
Top commit has no ACKs.
Tree-SHA512: c7d8e354996c673da36cc9add260383c82a5325bfaa7ce6141ad6cd6b7d6adf3a6c900ea2db17fb70147b3625fa7f6a1ff8ba813aeaa299f316d8f6cabb3a65c
Diffstat (limited to 'test')
0 files changed, 0 insertions, 0 deletions