Turns out fuzz builds are broken and probably have been broken for ~1 month since the last-tested revision for some open fuzz bugs is a month old.
My best guess for why we didn't get a notification is that our coverage build has been broken ~forever (expectedly) and they probably lump the two together. Alas.
Looking to fix this in https://github.com/google/oss-fuzz/pull/14753
Cause of this was https://github.com/bytecodealliance/wasmtime/pull/12119
@Chris Fallin or @fitzgen (he/him) do y'all (or anyone else) have contacts at Google we can ping about https://github.com/google/oss-fuzz/pull/14753?
I've pinged maintainers on that ~1 week apart twice and haven't gotten a response
Or, alternatively, one of y'all could try sending the same PR and see if it's just me who got deny-listed...
I don't have any contacts on the oss-fuzz team or adjacent :-/
hmm, I don't think I know anyone who's relevant unfortunately either
maybe we could ping our binaryen-team friends and ask if they can help unstick this?
that's a good point yeah, I'll give it a few more days then reach out to Sam/Thomas
Merged now, yay! Build succeeded and stale oss-fuzz bugs are closed now. All that's left is to prepare for a possible onslaught of stuff we missed in the meantime
Last updated: Feb 24 2026 at 04:36 UTC