On Sun, Aug 09, 2020 at 10:06:49PM -0600, Jeff Law wrote:
On Sun, 2020-08-09 at 12:02 +0200, Fabio Valentini wrote:
> On Sun, Aug 9, 2020 at 12:03 AM Jeff Law <law(a)redhat.com> wrote:
> > So I've done two passes over the F33 build failures here:
> >
> >
https://kojipkgs.fedoraproject.org/mass-rebuild/f33-failures.html
>
> Hi Jeff,
>
> Thanks for looking at the failures, it's really appreciated!
>
> Be aware that the f33-failures.html page is not complete though, since
> packages for which there was an attempted rebuild *after* the mass
> rebuild are removed from the list, whether the builds succeeded or
> not. So it's possible that you missed builds that fail for LTO-related
> issues, just because they're no longer showing up in the list. The
> list of bugs blocking the F33FTBFS bug in bugzilla [0] might be
> helpful here. And the f33-need-rebuild list [1] should give you a
> complete picture of everything that has not successfully been rebuilt
> for f33 yet.
ACK. I'm poking at the f33-need-rebuild.html list a bit. THere's a lot of
noise
in there -- things that haven't been built in a long time. Anyway, I'll keep
poking around.
It would be helpful if there was a clean way to download failed log files and
such in batches so that I could run tools on them to look for common things that
don't need my attention (like all the cmake failures). As it stands I have to do
an insane amount of clickies to get to some basic data.
It's been proposed to enable the koji 'save-failed-tree' plugin:
https://pagure.io/releng/issue/8243
It might help for this sort of thing, as it lets you get a complete tar
of the entire tree.
I'll look into it more after we have staging koji back...
kevin