Hi,

On 26-07-2022 13:28, Luca Boccassi wrote:
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.

This seems to have started on July the 22nd. List of recent failures:

https://ci.debian.net/packages/s/sbuild/testing/amd64/

Eg:

https://ci.debian.net/data/autopkgtest/unstable/amd64/s/sbuild/23951901/log.gz

+ mmdebstrap --mode=unshare --variant=apt unstable /tmp/chroot.tar
I: chroot architecture amd64 is equal to the host's architecture
I: automatically chosen format: tar
I: using /tmp/mmdebstrap.1Pi2WSLk6H as tempdir
I: running apt-get update...
I: downloading packages with apt...
I: extracting archives...
I: installing essential packages...
Selecting previously unselected package gcc-12-base:amd64.
(Reading database ... 0 files and directories currently installed.)
Preparing to unpack .../gcc-12-base_12.1.0-7_amd64.deb ...
Unpacking gcc-12-base:amd64 (12.1.0-7) ...
Selecting previously unselected package libc6:amd64.
Preparing to unpack .../libc6_2.33-8_amd64.deb ...
Use of uninitialized value in concatenation (.) or string at 
/usr/share/perl5/Debconf/Config.pm line 22.
Unpacking libc6:amd64 (2.33-8) ...
dpkg: error processing archive /var/cache/apt/archives/libc6_2.33-8_amd64.deb 
(--install):
  cannot copy extracted data for './usr/lib/x86_64-linux-gnu/gconv/IBM904.so' 
to '/usr/lib/x86_64-linux-gnu/gconv/IBM904.so.dpkg-new': failed to write (No 
space left on device)

That worker (ci-worker13) has 7 TB of disk available, so space shouldn't be the problem. I'm also not seeing [1] the disk usage anytime higher than 7% (and it's actually that /mnt/lxc-containers that's being used and that doesn't peak above 1.2% since we changed hosts).

Paul

[1] https://ci.debian.net/munin/ci-worker13/ci-worker13/df.html

Attachment: OpenPGP_signature
Description: OpenPGP digital signature

Reply via email to