[14:56] <enr0n> Can a core dev please retry the systemd autopkgtest regressions in jammy: retry-autopkgtest-regressions --blocks systemd -s jammy ?
[14:56] <enr0n> The s390x ones are testbed failures, and I believe the rest are flaky or at least deserve a retry.
[15:01] <jawn-smith> enr0n: on it
[15:05] <enr0n> jawn-smith: thanks!
=== Eickmeyer is now known as NotEickmeyer
=== Eickmeyer4 is now known as Eickmeyer
=== bdmurray changed the topic of #ubuntu-devel to: Archive: Kinetic Feature Freeze | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Bionic-Jammy | If you can't send messages here, authenticate to NickServ first | Patch Pilots:
=== sem2peie- is now known as sem2peie
[20:06] <jawn-smith> foka: Have you looked into the FTBFS of hugo at all?
[20:15] <foka> jawn-smith: Is there a FTBFS with hugo 0.102.3-1?
[20:15] <jawn-smith> In ubuntu, yes. It seems to have some failing tests on ppc64el
[20:16] <jawn-smith> I can look into it if you're busy. Just don't want to duplicate effort
[20:20] <foka> jawn-smith: Sorry, I wasn't aware that there was a FTBFS on ppc64el on Ubuntu. Were you referring to this? https://launchpad.net/ubuntu/+source/hugo/0.102.3-1/+build/24346618
[20:21] <foka> jawn-smith: I haven't looked at it yet, and likely no time today; if you don't mind looking into it, that would be great! Many thanks!
[20:22] <jawn-smith> Yes, that's the failed build. I will look into it! The version in release is depending on golang-1.18, and we would like to remove that before 22.10
[20:22] <jawn-smith> But the version in proposed depends on golang-1.19 instead, which solves that problem
[21:54] <waveform> any idea where we define the available disk space for an amd64 instance running autopkgtests? livecd-rootfs is consistently failing with "No space left on device" (which is all that's left blocking u-boot) and after diff'ing the logs against the last successful run, AFAICT it's just been tipped over the edge by one of the images it produces being ~40MB bigger than last time
[22:51] <xypron> waveform: When you run autopkgtests manually you can set the size of the image for the VM, see https://manpages.ubuntu.com/manpages/bionic/man1/autopkgtest-buildvm-ubuntu-cloud.1.html.  I would assume that it is a launchpad setting how big an image is used for the VM that launchpad uses. Maybe create a question for "launchpad  itself" (https://answers.launchpad.net/launchpad/+addquestion).
=== dbungert1 is now known as dbungert
[23:42] <dbungert> waveform: https://wiki.ubuntu.com/ProposedMigration#autopkgtests says the default is "similar to a m1.small", but that wiki entry only talks memory, cpu, and timeout.  Other online resources put m1.small on a 160G disk, do you think it's plausible that livecd-rootfs is hitting that?