Re: buildd chroot creation: who should get notified of failures?
On Thu, Dec 21, 2017 at 3:45 AM, Paul Wise <email@example.com> wrote:
> Hi folks,
> Occasionally the buildd (and porterboxen) fail to debootstrap updated
> chroots. Sometimes these are Internet problems, sometimes local network
> problems, sometimes mirror problems, sometimes archive problems. These
> mails go to DSA but as far as I can tell, we always ignore them, I
> certainly do. I have included below a sample of the error messages
> since September so folks can get an idea of the errors.
> Should they go to the buildd admins?
I think so, if buildd admins are responsible for buildds, that
includes chroots, so if those are broken, they should be able to fix
I also think debian-wb-team@ should get a copy of such failures, in
particular which buildd needs updating chroots, if that does not
involve much hassle. However, it'd be great if we could automate error
detection an re-trigger automatically its generation.
> Should we stop recording them altogether?
> Should we log them to disk instead of mailing them?
> Should we be sending these mails to other locations?
> Should DSA triage the mails and bounce them elsewhere?
> Other thoughts?
> W: Retrying failed download of http://mirror.bytemark.co.uk/debian/dists/sid/main/binary-arm64/Packages.gz
> W: http://mirror.bytemark.co.uk/debian/dists/sid/main/binary-arm64/Packages.gz was corrupt
> W: Failure while configuring base packages. This will be re-attempted up to five times.
> W: See /srv/buildd/unpack/create-sid-Iu8qOr/debootstrap/debootstrap.log for details (possibly the package libp11-kit0:kfreebsd-i386 is at fault)
> + chroot /srv/buildd/unpack/create-sid-QkPNAw apt-get update
> E: could not load seccomp policy: Invalid argument - HttpMethod::Configuration (22: Invalid argument)
> E: Failed getting release file http://ftp.br.debian.org/debian/dists/stretch/Release
> E: Failed to fetch http://mirror.bytemark.co.uk/debian/pool/main/p/policyrcd-script-zg2/policyrcd-script-zg2_0.1-3_all.deb Cannot initiate the connection to mirror.bytemark.co.uk:80
> (2001:41c8:20:5e6::10). - connect (101: Network is unreachable) [IP: 2001:41c8:20:5e6::10 80]
> W: Couldn't download package zlib1g (ver 1:1.2.8.dfsg-2+b1 arch armhf)
> E: Couldn't download packages: zlib1g
> E: Couldn't download dists/buster/main/binary-s390x/Packages
> E: Failed to fetch http://ftp.us.debian.org/debian/dists/buster/main/i18n/Translation-en.bz2 File has unexpected size (5503564 != 5506053). Mirror sync in progress? [IP: 126.96.36.199
> Hashes of expected file:
> - Filesize:5506053 [weak]
> - SHA256:619c777b9e48dc3b40072b3d5b69296be2929f9c304aafad266f50ee757f5a9f
> - MD5Sum:375174c54de2e90bb7861be479e2930e [weak]
> Release file created at: Sun, 17 Sep 2017 08:31:39 +0000
Héctor Orón -.. . -... .. .- -. -.. . ...- . .-.. --- .--. . .-.