On Tue, 2022-07-26 at 15:15 +0200, Johannes Schauer Marin Rodrigues wrote: > Hi, > > thank you for your bug report! > > Quoting Luca Boccassi (2022-07-26 13:28:50) > > Severity: serious > > why is an autopkgtest failure "serious"?
Because it blocks other packages from migrating to testing, e.g.: https://tracker.debian.org/pkg/apt If it's not appropriate, please do update it accordingly, but IIRC it's what gets used in these cases. > > The autopkgtest run for sbuild keeps failing in debci, blocking other > > packages migrations. The failure manifests in two different error > > types, but both related to "No space left on device" when running > > mmdebstrap. > > The reason for this is the upload of gcc-defaults 1.198 to unstable. I > bisected > Debian unstable. On 2022-07-22T08:51:38Z a buildd chroot tarball was 396 MB > small. Starting with snapshot timestamp 2022-07-22T15:09:35Z (the first > timestamp with the new gcc-defaults version) a buildd chroot tarball is now > 906 > MB large. > > I put the gcc maintainer in CC. Is the buildd tarball to be more than twice > the > size compared to before now? > > Thanks! Good find - regardless of whether it's intended that the tarball is so large, perhaps it is an indication that the sbuild testsuite is a bit fragile w.r.t. the running environment? Would it be possible to adjust it to be more resilient? Is there a different disk-based scratch area available for test artifacts? -- Kind regards, Luca Boccassi
signature.asc
Description: This is a digitally signed message part
