Your message dated Sat, 13 Feb 2021 21:59:01 +0100
with message-id <68a2c568-9bbd-f141-cb26-563617ea3...@debian.org>
and subject line Re: autopkgtest flaky on arm64
has caused the Debian Bug report #977268,
regarding autopkgtest flaky on arm64
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
977268: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977268
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:puppet
Version: 5.5.22-1
Severity: serious
X-Debbugs-Cc: debian...@lists.debian.org
Hi,
it appears the autopkgtest of puppet is not really stable on arm64.
https://ci.debian.net/packages/p/puppet/testing/arm64/
I scheduled it a couple of times, as its results were blocking systemd
from testing migration. The refrence run sometimes failed, sometimes
succeeded.
Filing with severity serious, as nowadays the test results affect other
packages.
Regards,
Michael
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.9.0-4-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Hi,
On Sun, 13 Dec 2020 13:12:08 +0100 Michael Biebl <bi...@debian.org> wrote:
> it appears the autopkgtest of puppet is not really stable on arm64>
> https://ci.debian.net/packages/p/puppet/testing/arm64/
Hmm. It looks like in the last 8 months, it only *really* failed [1]
with the systemd tests and 1 migration-reference/0 run. I noticed that
in those logs, there were 2 versions of libboost files installed. I
suspect it's related to a libboost transition.
I'm closing this bug, as I don't believe puppet is really to blame here.
Paul
[1] other failures were network issues.
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
