-
Notifications
You must be signed in to change notification settings - Fork 266
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
Fix a case where fuzz_target_path
is mysteriously None
#1886
Conversation
Not sure this is a good idea. I'm more interested in why this fails. I think this fix could potentially mess up results. If one fuzzer is messing with paths and we can't use the seed corpus it's better it fails then runs without using the seed corpus when others do use it (skewing the results) |
And these other fuzzers do appear to find the seed corpus: https://www.fuzzbench.com/reports/experimental/2023-08-04-sfuzz/index.html |
+1 we should fix the root cause here, rather than papering over issues. |
I agree that it's better to let it run without using the seeds: I thought that's the intention of this PR? But finding the root cause is a better idea. I will look further into that. |
We don't agree :-) I think it's better to produce a noticeable failure than a subtly incorrect failure.
|
Oh, I see! |
Closing this as we will address it in new PRs. |
This was observed in this experiment. Here is the error log:
I could not reproduce this error locally, but this PR should fix the error.