-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
urllib3: Fuzzer missing from code coverage #9863
Comments
I think is probably because the fuzzer is having some trouble running, am seeing this issue:
This probably affects such that the fuzzer either failed to generate corpus or was not run in a manner such that atheris was exited proper (sys.exit(0)) which is needed for coverage runs. Note the proper exit will be handled by the infrastructure if the fuzzer does not e.g. throw exceptions on a normal run. Therefore, it's likely the above exception is thrown on the first iteration of |
Thanks for finding this @DavidKorczynski . I'll do some research on where the issue is occurring. I can run this locally on my Ubuntu 20.04 setup without exception (i.e. I couldn't find the exception you've shared on the introspector reports or this build dashboard https://oss-fuzz-build-logs.storage.googleapis.com/index.html#urllib3. How did you see this exception? I'd like the see the rest of the logs in-case there's something I'm missing like a port binding issue when starting the test HTTP server. |
This was an issue reported by OSS-Fuzz to the list of emails in the To get experience with the end-to-end OSS-Fuzz approach I think a good approach is to carry out an initial integration of some project where you've reached out the maintainers beforehand to ask if it's okay for you to see potential issues being raised. If the maintainers are happy with this then you can put your email in the |
I've managed to recreate the issue that was stopping the `fuzz_requests` coverage on `urllib3` ( see #9863 ) The issues not visible running introspector locally but can be see in clusterfuzzlite which is a port binding error. This change randomises the port that's used and ensures that it can bind to it before fuzzing starts. Change is tested and demonstrated as working here [sg3-141-592/urllib3 - ClusterFuzzLite PR fuzzing](https://github.com/sg3-141-592/urllib3/actions/runs/4466205991/jobs/7844093473?pr=1). Also I've changed the style of the main block and atheris to be consistent with the other fuzzers added lately.
When reviewing the code coverage for urllib3 the coverage for
fuzz_requests.py
is missing from the report.https://storage.googleapis.com/oss-fuzz-introspector/urllib3/inspector-report/20230305/fuzz_report.html
We can see
fuzz_requests
in the introspector reportbut
fuzz_requests.py
isn't in the coverage report, and also the coverage from this fuzzer is missing in the report.The text was updated successfully, but these errors were encountered: