Bug#980111: pam breaks frr autopkgtest on armhf and ppc64el: non-zero exit status 1

2021-01-16 Thread Ivo De Decker
Control: reassign -1 frr/7.4-1

Hi,

On Thu, Jan 14, 2021 at 05:00:26PM +0100, Paul Gevers wrote:
> With a recent upload of pam the autopkgtest of frr fails in testing on
> armhf and ppc64el when that autopkgtest is run with the binary packages
> of pam from unstable. It passes when run with only packages from
> testing. In tabular form:
> 
>passfail
> pamfrom testing1.4.0-2
> frrfrom testing7.4-1
> all others from testingfrom testing

> autopkgtest [11:36:52]: test py-frr-reload: [---

Paul gave me access to a machine similart to the one that's running the test
on armhf. It looks like it's a race condition in the test itself (or in the
frr scripts):

The test runs 
  service frr reload
and then runs
  vtysh -c 'show running-config'
to check if the output is changed. With the new pam, this command still shows
the old config immediately after the reload. A few seconds later, it shows the
new config. I suspect the changes in pam affect the timing of some of the
steps involved.

As it looks like this is an issue in the frr test (or the frr package), I'm
reassigning the bugs there.

Cheers,

Ivo



Bug#980111: pam breaks frr autopkgtest on armhf and ppc64el: non-zero exit status 1

2021-01-14 Thread Paul Gevers
Source: pam, frr
Control: found -1 pam/1.4.0-2
Control: found -1 frr/7.4-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org, iv...@debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of pam the autopkgtest of frr fails in testing on
armhf and ppc64el when that autopkgtest is run with the binary packages
of pam from unstable. It passes when run with only packages from
testing. In tabular form:

   passfail
pamfrom testing1.4.0-2
frrfrom testing7.4-1
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of pam to testing
[1]. Due to the nature of this issue, I filed this bug report against
both packages. Can you please investigate the situation and reassign the
bug to the right package?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=pam

https://ci.debian.net/data/autopkgtest/testing/armhf/f/frr/9682558/log.gz

autopkgtest [11:36:52]: test py-frr-reload: [---
1634
1647
1652
Note: this version of vtysh never writes vtysh.conf
Building Configuration...
Integrated configuration saved to /etc/frr/frr.conf
[OK]
autopkgtest [11:36:54]: test py-frr-reload: ---]




OpenPGP_signature
Description: OpenPGP digital signature