Build failures aren't reported by OSS-Fuzz #13289
Comments
|
I am having the same problem i see that someone did #13331 but i was not informed at all that poppler was failing. This used to work. |
|
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) |
|
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/. |
|
Sorry I didn't read the issue close enough, I will look into this after the long weekend |
|
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. |
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 #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.
The text was updated successfully, but these errors were encountered: