On Wed, 2023-06-28 at 13:23 +0200, Ondřej Budai wrote:
> We can definitely flatten the JSON output into something that resembles a
> log file. I will let you know when this is done.
>
> Note that every task also produces a manifest file - this is extremely
> useful, because you can just feed it to osbuild locally. Since the manifest
> basically fully specifies an image build (with locked package versions
> including their hashes), there's a high chance that you will be just able
> to reproduce the issue locally and use any tools you want for deeper
> debugging. This is one of the goals of the project: Make image builds more
> reproducible.
Unless the tool can pull older builds directly from Koji, I don't see
how this will work for more than a day or so. It's a cool capability,
but it seems to hinge on older builds being available, which they kinda
aren't very easily.
Reproducibility is awesome, but it doesn't replace good debug output.
For a start, you still need the useful output to debug the problem when
you reproduce it. And second, I assume building a live image is still
gonna take a significant amount of time, like 30 minutes? Typically, we
can debug a simple live image failure in about thirty seconds ("oh,
look at anaconda.log, it failed because of a broken dependency" is the
most common scenario) and probably fix it in less time than it would
take to reproduce the build.
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @[email protected]
https://www.happyassassin.net
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
