oss-fuzz icon indicating copy to clipboard operation
oss-fuzz copied to clipboard

Build failures aren't reported by OSS-Fuzz

Open evverx opened this issue 8 months ago • 7 comments

dbus-broker started failing to build on April 29 but as far as I can see it hasn't been reported by OSS-Fuzz (at least I can't seem to find any bug reports anywhere on https://issues.oss-fuzz.com/. Notifications haven't been sent either).

dbus-broker was fixed in https://github.com/google/oss-fuzz/pull/13286 so it should turn green soon but for example lxc has been failing to build due to the same meson regression and as far as I can see those build failures are shown at https://oss-fuzz-build-logs.storage.googleapis.com/index.html#lxc / https://introspector.oss-fuzz.com/project-profile?project=lxc only.

evverx avatar May 07 '25 15:05 evverx

I am having the same problem i see that someone did https://github.com/google/oss-fuzz/pull/13331 but i was not informed at all that poppler was failing.

This used to work.

tsdgeos avatar May 20 '25 22:05 tsdgeos

Are your email addresses non-google accounts? we basically can't email these anymore and don't have an easy way of doing this (were working on a hard way)

jonathanmetzman avatar May 23 '25 18:05 jonathanmetzman

I receive notification from OSS-Fuzz (the latest notification was sent today at 18:37). As far as I understand the problem is that the build failures weren't reported at all at https://issues.oss-fuzz.com/.

evverx avatar May 23 '25 19:05 evverx

Sorry I didn't read the issue close enough, I will look into this after the long weekend

jonathanmetzman avatar May 23 '25 21:05 jonathanmetzman

Looking at https://issues.oss-fuzz.com/issues/417369000 and https://issues.oss-fuzz.com/issues/418896502 it seems some build failures were reported recently so it could have been a glitch or something like that. If it reliably works now I think this issue can be closed.

evverx avatar May 24 '25 10:05 evverx

To judge from https://issues.oss-fuzz.com/issues/421055129 OSS-Fuzz reports some build failures. https://oss-fuzz-build-logs.storage.googleapis.com/index.html#avahi

Image

What's weird though is that systemd failed to build similarly https://oss-fuzz-build-logs.storage.googleapis.com/index.html#systemd

Image and it wasn't reported.

evverx avatar May 29 '25 23:05 evverx

I just realized that builds for our project (igraph) were failing for over 2 weeks, but I did not receive an email notification. I do have a Gmail address registered with OSS-fuzz.

The build failures are shows correctly in the web interface, but I did not receive emails about them. As I recall, in the past an email was send after about 3 (?) failures.

szhorvat avatar Jun 03 '25 22:06 szhorvat

For the record dbus-broker has been failing to build (because it needs rustc and bindgen now https://github.com/google/oss-fuzz/pull/13299) but it hasn't been reported by OSS-Fuzz as far as I can see.

https://oss-fuzz-build-logs.storage.googleapis.com/index.html#dbus-broker Image

evverx avatar Jun 20 '25 11:06 evverx

For the record the dbus-broker build failure was reported eventually in https://issues.oss-fuzz.com/issues/432299042 so it took about a month for it to be opened for some reason.

evverx avatar Jul 18 '25 12:07 evverx

I think it got weirder. OSS-Fuzz reported recent avahi build failures (https://issues.oss-fuzz.com/issues/444070635) and closed it when https://github.com/google/oss-fuzz/pull/13968 was merged as expected. systemd started failing to build at the same time and still keeps failing to build because of https://github.com/google/oss-fuzz/issues/13975 but it hasn't been reported yet.

evverx avatar Sep 11 '25 03:09 evverx