Your message dated Sun, 16 Aug 2015 13:43:39 +0200
with message-id <[email protected]>
and subject line Re: Bug#789830: unreproducible / pbuilder vs. sbuild
has caused the Debian Bug report #789830,
regarding libterm-filter-perl: FTBFS in sid: test failures
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 [email protected]
immediately.)
--
789830: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789830
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: libterm-filter-perl
Version: 0.03-1
Severity: serious
Justification: FTBFS
This package FTBFS in a clean sid sbuild setup:
# Failed test 'munge_input and munge_output got the right arguments'
# at t/callbacks.t line 70.
# 'MUNGE_INPUT: Term::Filter::Callback=HASH(0x20e7f50)
(Term::Filter::Callback): fOo
#
# MUNGE_OUTPUT: Term::Filter::Callback=HASH(0x20e7f50)
(Term::Filter::Callback): FOO
#
# foo
# MUNGE_OUTPUT: Term::Filter::Callback=HASH(0x20e7f50)
(Term::Filter::Callback): FOO
# fooMUNGE_OUTPUT: Term::Filter::Callback=HASH(0x20e7f50)
(Term::Filter::Callback):
#
#
# '
# doesn't match '(?^sx:
# ^
# MUNGE_INPUT: \s Term\:\:Filter\:\:Callback\=HASH\(0x20e7f50\) \s
\(Term::Filter::Callback\): \s fOo\n
# \n
# (?:
# MUNGE_OUTPUT: \s Term\:\:Filter\:\:Callback\=HASH\(0x20e7f50\) \s
\(Term::Filter::Callback\): \s FOO(?^:\x0d\x0a)
# \n
# foo(?^:\x0d\x0a)
# MUNGE_OUTPUT: \s Term\:\:Filter\:\:Callback\=HASH\(0x20e7f50\) \s
\(Term::Filter::Callback\): \s FOO(?^:\x0d\x0a)
# \n
# foo(?^:\x0d\x0a)
# |
# MUNGE_OUTPUT: \s Term\:\:Filter\:\:Callback\=HASH\(0x20e7f50\) \s
\(Term::Filter::Callback\): \s FOO(?^:\x0d\x0a) FOO(?^:\x0d\x0a)
# \n
# foo(?^:\x0d\x0a)
# foo(?^:\x0d\x0a)
# )
# $
# )'
# Looks like you failed 1 test of 3.
t/callbacks.t .............
ok 1 - setup callback got a Term::Filter::Callback 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
t/extra-pty.t .............
ok 1
ok 2
ok 3
ok 4
ok 5
ok 6
1..6
ok
t/release-eol.t ........... skipped: these tests are for release candidate
testing
t/release-no-tabs.t ....... skipped: these tests are for release candidate
testing
t/release-pod-coverage.t .. skipped: these tests are for release candidate
testing
t/release-pod-syntax.t .... skipped: these tests are for release candidate
testing
t/requires-tty.t ..........
ok 1 - requires a terminal
ok 2 - requires a terminal
1..2
ok
# Failed test 'munge_input and munge_output got the right arguments'
# at t/role.t line 79.
# 'MUNGE_INPUT: My::Term::Filter=HASH(0x1e8d2f0)
(My::Term::Filter): fOo
#
# MUNGE_OUTPUT: My::Term::Filter=HASH(0x1e8d2f0) (My::Term::Filter): FOO
#
# foo
# MUNGE_OUTPUT: My::Term::Filter=HASH(0x1e8d2f0) (My::Term::Filter): FOO
# fooMUNGE_OUTPUT: My::Term::Filter=HASH(0x1e8d2f0) (My::Term::Filter):
#
#
# '
# doesn't match '(?^sx:
# ^
# MUNGE_INPUT: \s My\:\:Term\:\:Filter\=HASH\(0x1e8d2f0\) \s
\(My::Term::Filter\): \s fOo\n
# \n
# (?:
# MUNGE_OUTPUT: \s My\:\:Term\:\:Filter\=HASH\(0x1e8d2f0\) \s
\(My::Term::Filter\): \s FOO(?^:\x0d\x0a)
# \n
# foo(?^:\x0d\x0a)
# MUNGE_OUTPUT: \s My\:\:Term\:\:Filter\=HASH\(0x1e8d2f0\) \s
\(My::Term::Filter\): \s FOO(?^:\x0d\x0a)
# \n
# foo(?^:\x0d\x0a)
# |
# MUNGE_OUTPUT: \s My\:\:Term\:\:Filter\=HASH\(0x1e8d2f0\) \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.
Failed 2/10 test programs. 2/19 subtests failed.
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/callbacks.t (Wstat: 256 Tests: 3 Failed: 1)
Failed test: 2
Non-zero exit status: 1
t/role.t (Wstat: 256 Tests: 3 Failed: 1)
Failed test: 2
Non-zero exit status: 1
Files=10, Tests=19, 17 wallclock secs ( 0.05 usr 0.08 sys + 3.79 cusr 0.47
csys = 4.39 CPU)
Result: FAIL
Cheers,
Dominic.
--- End Message ---
--- Begin Message ---
On Thu, Jul 02, 2015 at 05:19:12PM +0200, gregor herrmann wrote:
> Control: tag -1 + unreproducible
>
> On Thu, 25 Jun 2015 22:09:28 +0200, Salvatore Bonaccorso wrote:
>
> > On Thu, Jun 25, 2015 at 09:52:53PM +0200, gregor herrmann wrote:
> > > I can't reproduce these 2 bugs.
> > > Apparently #789828 happens only with sbuild and not with p/cowbuiler,
> > > maybe #789830 falls into the same category ...
> >
> > Can't neither preproduce #789830 FTBFS for libterm-filter-perl (with
> > sbuild).
> > But have not done any further check so far.
>
> Thanks for trying!
>
> For me, libterm-filter-perl builds with cowbuilder/unstable,
> cowbuilder/exp-perl5.22 and the (autopkg)tests also pass in
> sbuild/unstable (all 3 amd64) and cowbuilder/unstable/i386.
>
> Dom, any idea? Can you reproduce the problem?
> Anything we should know/check?
Hi,
I can't reproduce this either, so it must have been something
temporary on my system.
Sorry for the noise and thanks for checking!
Dominic.
--- End Message ---
