| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
…figparser (pythonGH-143929) (cherry picked from commit 5858e42) Co-authored-by: Seth Larson <seth@python.org>
|
Fuzzer failures look unrelated. @python/fuzzers, could you give me CIFuzz access so I'm able to investigate? (Contacting you per devguide.) |
Sorry, something went wrong.
I'm not sure what you mean? The logs are public as it's ran in the CI. The workflow for CI fuzz is also in this repository, the targets live here or in library-fuzzers. |
Sorry, something went wrong.
|
The errors aren't new, to fix it we can just add the exceptions (LookupError in plistlib, OverflowError in ast) to our try/except blocks to catch them, but I raised the bigger question of whether we should even maintain the targets for older versions: python/library-fuzzers#56 |
Sorry, something went wrong.
|
Oh, CI-Fuzz and OSS-Fuzz are different things. Sorry for the noise! |
Sorry, something went wrong.
|
Yep, we run CI-Fuzz. If you want to join us in OSS-Fuzz land, you'll have to open a PR in Google's repository to gain access, I'm afraid we don't technically have control over it. Ping me over there and I'll approve it :-) |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
(cherry picked from commit 5858e42)
Co-authored-by: Seth Larson seth@python.org