[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#917805: marked as done (release.debian.org: autopkgtests wrongly assume that package work in testing)

Your message dated Thu, 7 Mar 2019 09:29:07 +0100
with message-id <f637aa27-7bb5-8217-caac-934d43692035@debian.org>
and subject line Re: release.debian.org: autopkgtests wrongly assume that package work in testing
has caused the Debian Bug report #917805,
regarding release.debian.org: autopkgtests wrongly assume that package work in testing
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 owner@bugs.debian.org
immediately.)


-- 
917805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917805
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal

The upload of glibc 2.28-4 has trigger the pacemaker autopkgtest, which
failed due to bug#917801, caused by the migration of corosync 3.0.0-1 to
testing on 2018-12-26:

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pacemaker/1613604/log.gz

It is considered as a regression introduced by the glibc upload, as the
reference used is the following from 2018-12-24, which still uses
corosync 2.4.4-3.

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pacemaker/1581332/log.gz

I believe the autopkgtests should not assume that a package still works
in testing if it has worked at some point in the past. The best would be
to retry the tests purely in testing if the one from testing + tested
package fail.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

--- End Message ---
--- Begin Message --- 
Hi Aurelien,

On Sun, 30 Dec 2018 15:10:27 +0100 Aurelien Jarno <aurel32@debian.org>
wrote:
> I believe the autopkgtests should not assume that a package still works
> in testing if it has worked at some point in the past. The best would be
> to retry the tests purely in testing if the one from testing + tested
> package fail.

The migration software has been improved to ignore results from versions
not in unstable or testing. So the case in this bug report shouldn't
happen anymore.

https://salsa.debian.org/release-team/britney2/commit/992b27a

Paul

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
Reply to: