-
Notifications
You must be signed in to change notification settings - Fork 19
fix broken fuzz target compile_parse_tree
#162
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
base: master
Are you sure you want to change the base?
fix broken fuzz target compile_parse_tree
#162
Conversation
|
Nice, thanks!! Code review ACK -- running through my local CI and also Github CI will run. Hopefully it passes. Stuff like this is often really annoying to get right.. |
|
@lucasbalieiro ok, this isn't working for me with my local crate2nix setup, because when I run I would like you to remove all the The most straightforward thing might be to just copy all the boilerplate from rust-simplicity. e.g. https://github.com/BlockstreamResearch/rust-simplicity/blob/master/fuzz/fuzz_targets/c_rust_merkle.rs In particular the actual fuzz target should be gated on to fuzz/Cargo.toml. |
f88a2d1 to
881f454
Compare
|
@apoelstra sorry for the delay, I’m traveling at the moment. In 881f454, I applied the same style you suggested in Now, when you ignore |
|
No worries. I have been traveling too. Can you re-arrange these commits (using |
this replaces `named::to_commit_node` with `named::forget_names`
881f454 to
445ae20
Compare
done! commits re-arranged |
closes #161
updates the outdated fuzz target
compile_parse_tree.It was still using
named::to_commit_node, which has since been replaced bynamed::forget_names(see this commit)Also (as suggested in the issue discussion):
fuzzfrom the exclude list inCargo.tomland add to workspace memberscargo checkthe fuzz crate