Build failures aren't reported by OSS-Fuzz

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.

Start with the lxc build logs and project profile linked in the issue, then compare them with the dbus-broker failure and the fix in google/oss-fuzz#13286. Trace how build failures are expected to become OSS-Fuzz bug reports and notifications. Done means reproducing the missing report or notification and documenting or fixing the reporting path.

Written by the indexing model from the issue text.