On Sun, Dec 30, 2018 at 03:10:27PM +0100, Aurelien Jarno wrote:
> 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
So it seems.
> 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.
Anybody with a SSO certificate can request a test, and in particular
triggering the migratin-reference test of pacemaker again would be
enough to update the base status and turn the "regression" into a
regular failure.
However, ISTM that the fixed pacemaker is going to migrate tonight if
everything goes well, so just waiting and seeing tomorrow, and retrying
the glibc test tomorrow will be enough (and actually better, as if you
were doing to do the former it would bump up the migration delay).
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
Attachment:
signature.asc
Description: PGP signature