-
Notifications
You must be signed in to change notification settings - Fork 37.7k
fuzz: Create a block template in tx_pool targets #21798
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…dcoding a maximum size This is technically a breaking change. This allows the fuzz engine to pick the right size, also larger sizes, if needed.
This is needed for the next commit to generate blocks. Also, apply the same mocking strategies to both targets.
Concept ACK Touches only |
Looks like ci fails due to:
|
(ci now green) |
Tested fa03232 with DEBUG=1 and observed some nice coverage increases. My setup is still showing the CI's UB error both in faf3e9d and fa03232, but that just might be due to my own lack of understanding or a compile issue on my part. |
squashed the commits. bisecting should now work again. |
Tested ACK fa03d0a As expected the coverage achieved by the Nice work! |
fa03d0a fuzz: Create a block template in tx_pool targets (MarcoFalke) fa61ce5 fuzz: Limit mocktime to MTP in tx_pool targets (MarcoFalke) fab646b fuzz: Use correct variant of ConsumeRandomLengthString instead of hardcoding a maximum size (MarcoFalke) fae2c8b fuzz: Allow to pass min/max to ConsumeTime (MarcoFalke) Pull request description: Relatively simple check to ensure a block can always be created from the mempool ACKs for top commit: practicalswift: Tested ACK fa03d0a Tree-SHA512: e613376ccc88591cbe594db14ea21ebc9b2b191f6325b3aa4ee0cd379695352ad3b480e286134ef6ee30f043d486cf9792a1bc7e44445c41045ac8c3b931c7ff
Relatively simple check to ensure a block can always be created from the mempool