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
CIFuzz has started failing #5324
Comments
They must have just added code coverage support for python. I'll see what it takes to support that, in the meantime I wonder if we can make this a soft fail in GHA? |
I'm not seeing anything upstream that would indicate code coverage for python is working yet. It actually looks like this is the issue:
|
In that case, I wonder if adding |
Possibly -- but it's not failing on my local builds where I'm running the fuzzer. It looks like it's failing with that on the oss-fuzz level as well @ google, so I'll look into it today. |
I see that #5328 had a fix for this, so we're waiting on google/oss-fuzz#5522. But now valgrind is failing in master? |
Yes, valgrind is erroring, and it's failing on a few images in the fuzz testing. It's possible that this is another run of the same issues that we've got ignored elsewhere, and it's possible that it's something new. |
CIFuzz is now passing again. |
Huh. I wonder why that is., because my pr hasn’t been merged. |
I think this is why - google/oss-fuzz#5552 |
For the record, the valgrind issues were solved by #5397 |
CIFuzz has started failing. As a demo, with the meaningless change from radarhere@510a5a3, I get https://github.com/radarhere/Pillow/runs/2084858912
I think the relevant part is
But strangely, looking back for a passing run - https://github.com/python-pillow/Pillow/runs/2049950863
The text was updated successfully, but these errors were encountered: