Public bug reported:
[Impact]
When we encounter a failure in 'lb binary' the launchpad builders can
only surface the build output from stdout. If the binary hook failure
implicates the archive we can not determine fault without the apt
proxy log. Backporting the patch from eoan will dump the proxy log
to stdout to aid in debugging these failures.
[Test case]
Run a build with a $REPO_SNAPSHOT_STAMP and a binary hook with 'exit 1'.
The apt proxy log should end up on stdout.
[Regression Potential]
Nearly none. This dumps a file to stdout in the failure exit path; a
failure at this stage does not change the outcome of the build.
[Other Info]
We are seeing issues today in builds that need this debug output in
place, we would like to move this SRU through quickly. The code has
been running in eoan for at least a week without issue.
** Affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847300
Title:
[backport] magic-proxy: dump proxy log to stdout on failure
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1847300/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
