On Mon, 11 May 2015 21:40:32 +0300, Niko Tyni wrote: > The failure mode looks weird, interleaving output streams or something > like that? It's reproducible locally for me. > > http://ci.debian.net/packages/libt/libterm-progressbar-perl/unstable/amd64/ > > t/02_term_progressbar_io.t .. > ok 1 - use Term::ProgressBar::IO; > ok 2 - Correct number of bytes in __DATA__ > 21ok 3 - Last position is now target > 1..3 > Failed 1/3 subtests > [...] > Test Summary Report > ------------------- > t/02_term_progressbar_io.t (Wstat: 0 Tests: 2 Failed: 0) > Parse errors: Bad plan. You planned 3 tests but ran 2. > Files=11, Tests=124, 12 wallclock secs ( 0.10 usr 0.09 sys + 1.53 cusr > 0.48 csys = 2.20 CPU) > Result: FAIL
I guess this is somehow related to the handling of stderr in
autopkgtest. The test file does:
19 ok($pb->target() == 9*2+3,'Correct number of bytes in __DATA__');
20
21 while (<$fh>) {
22 $err = capture_stderr {
23 $pb->update();
24 };
25 }
26
27 print STDERR $pb->last_update();
Not sure what we can do best here; allow stderr in autopkgtest or
disble this test, or something else?
Cheers,
gregor
--
.''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
: :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/
`. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
`- NP: The Who: Boris The Spider
signature.asc
Description: Digital Signature
