Bug#935017: debhelper breaks strip-nondeterminism autopkgtest

[Niels Thykier]

Control: reassign -1 strip-nondeterminism


On Sun, 18 Aug 2019 08:19:37 +0200 Paul Gevers <elbrus at debian.org> wrote:
> Source: debhelper, strip-nondeterminism
> Control: found -1 debhelper/12.5.1
> Control: found -1 debhelper/12.5
> Control: found -1 strip-nondeterminism/1.5.0-1
> Severity: serious
> X-Debbugs-CC: debian-ci at lists.debian.org
> User: debian-ci at lists.debian.org
> Usertags: breaks needs-update
> 
> Dear maintainers,
> 
> With a recent upload of debhelper the autopkgtest of
> strip-nondeterminism fails in testing when that autopkgtest is run with
> the binary packages of debhelper from unstable. It passes when run with
> only packages from testing. In tabular form:
>                        pass            fail
> debhelper              from testing    12.5.1
> strip-nondeterminism   from testing    1.5.0-1
> all others             from testing    from testing
> 
> I copied some of the output at the bottom of this report.
> 
> Currently this regression is blocking the migration of debhelper 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=debhelper
> 
> https://ci.debian.net/data/autopkgtest/testing/amd64/s/strip-nondeterminism/2758965/log.gz
> 
> 1..2
> not ok 1 - bin/dh_strip_nondeterminism --help returns 255
> 
> #   Failed test 'bin/dh_strip_nondeterminism --help returns 255'
> #   at t/binaries.t line 42.
> ok 2 - bin/strip-nondeterminism --help returns 0
> # Looks like you failed 1 test of 2.
> 

I cannot reproduce this locally in a sane way. For me, it returned 1
before and after upgrading to debhelper/12.5.1 (from 12.4).  Digging in
the tests, it looks like strip-nondeterminism is *not* testing the
installed binaries[1].

So for now I am punting it to strip-nondeterminism (even if only on a
technicality).  If you can dig out the real problem, please reassign
back/file a bug as appropriate.


Thanks,
~Niels

[1]:
https://salsa.debian.org/reproducible-builds/strip-nondeterminism/blob/master/t/binaries.t