Bug#843052: libterm-filter-perl: FTBFS randomly (failing tests)

[gregor herrmann]

On Thu, 03 Nov 2016 14:02:55 +0100, Santiago Vila wrote:

> I tried to build this package in stretch with "dpkg-buildpackage -A"
> (which is what the "Arch: all" autobuilder would do to build it)
> but it failed:

> #   Failed test 'munge_input and munge_output got the right arguments'
> #   at t/role.t line 79.
> #                   'MUNGE_INPUT: My::Term::Filter=HASH(0x23a3110) (My::Term::Filter): fOo
> # 
> # MUNGE_OUTPUT: My::Term::Filter=HASH(0x23a3110) (My::Term::Filter): FOO
> 
> # 
> # foo
> 
> # MUNGE_OUTPUT: My::Term::Filter=HASH(0x23a3110) (My::Term::Filter): FOO
> # fooMUNGE_OUTPUT: My::Term::Filter=HASH(0x23a3110) (My::Term::Filter): 
> 
> # 
> # 
> 
> # '
> #     doesn't match '(?^sx:
> #             ^
> #             MUNGE_INPUT: \s My\:\:Term\:\:Filter\=HASH\(0x23a3110\) \s \(My::Term::Filter\): \s fOo\n
> #             \n
> #             (?:
> #             MUNGE_OUTPUT: \s My\:\:Term\:\:Filter\=HASH\(0x23a3110\) \s \(My::Term::Filter\): \s FOO(?^:\x0d\x0a)
> #             \n
> #             foo(?^:\x0d\x0a)
> #             MUNGE_OUTPUT: \s My\:\:Term\:\:Filter\=HASH\(0x23a3110\) \s \(My::Term::Filter\): \s FOO(?^:\x0d\x0a)
> #             \n
> #             foo(?^:\x0d\x0a)
> #             |
> #             MUNGE_OUTPUT: \s My\:\:Term\:\:Filter\=HASH\(0x23a3110\) \s \(My::Term::Filter\): \s FOO(?^:\x0d\x0a) FOO(?^:\x0d\x0a)
> #             \n
> #             foo(?^:\x0d\x0a)
> #             foo(?^:\x0d\x0a)
> #             )
> #             $
> #         )'
> # Looks like you failed 1 test of 3.
> t/role.t .................. 
> ok 1 - setup callback got a My::Term::Filter object
> not ok 2 - munge_input and munge_output got the right arguments
> ok 3 - cleanup got the right arguments
> 1..3
> Dubious, test returned 1 (wstat 256, 0x100)
> Failed 1/3 subtests 
> 
> Test Summary Report
> -------------------
> t/role.t                (Wstat: 256 Tests: 3 Failed: 1)
>   Failed test:  2
>   Non-zero exit status: 1
> Files=10, Tests=19, 16 wallclock secs ( 0.05 usr  0.01 sys +  2.60 cusr  0.23 csys =  2.89 CPU)
> Result: FAIL

When I run the tests in a loop, under heady load, I can sometimes,
after quite some time, reproduce the failure in t/role.t (not the
others from the logs). The setting of TERM doesn't seem to be
relevant.

There's no upstream bug report (yet, will forward this one), and
there are rare occurences of the test failures on cpantesters:
http://matrix.cpantesters.org/?dist=Term-Filter+0.03


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Rolling Stones: Love-in-vain
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: Digital Signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-perl-maintainers/attachments/20161111/ed579ce2/attachment.sig>