#9650 No logs attached to FTBFS bugzilla
Closed: Fixed 3 years ago by mohanboddu. Opened 3 years ago by churchyard.

I've got a F33FTBFS bugzilla opened by releng: https://bugzilla.redhat.com/show_bug.cgi?id=1863149

There are no build logs attached there. Is that expected?


I assume that it might be more helpful to rebuild the packages instead of filing bugzillas about such failures, WDYT?

There's a number of things that could cause koji not to get to the point of making logs. Just blindly always resubmitting them would give us some kind or loop...

That said we DID resubmit all the failed builds from the first pass.

Did you resubmit the failed build here? or issue a new build?

Actually we tried, but what happened is some of them still failed in the second pass as well.

And the filing script is using the first one failed build, I asked @humaton to fix it but I guess its too late already :pensive:

From the stand up today:

[14:18:58] <nirik> so... let me try and explain.
[14:19:28] <nirik> 1. the FTBFS bugzilla bug filier is attaching the logs from the FIRST mass rebuild pass. Not the second one.
[14:19:48] <nirik> I don't know if that can easily be fixed.
[14:20:12] <nirik> There's a number of s390x failures that happened at different times.
[14:20:14] <mboddu> huh...
[14:21:00] <nirik> a) The repo is DELETED thing. That was monday morning. I had set kojira to expire repos really quickly to remove space. I fixed it monday. It should only afftect some range of packages monday morning and shouldn't affect anything after that
[14:21:50] <nirik> b) There was a problem with the varnish cache on wed night. It messed up a bunch of builds, it's fixed and shouldn't have affected any after
[14:22:31] <nirik> c) The random transitory 'can't read header' or 'failed to download package' cache issues. Those still affected some builds even after both passes, but decathrope is resubmitting them.

Metadata Update from @mohanboddu:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata