On Thu, 23 Dec 2021 21:59:45 +0100, Paul Gevers wrote: > With a recent upload of libio-async-perl the autopkgtest of libio-async-perl > fails in testing on ppc64el when that autopkgtest is run with the binary > packages of libio-async-perl from unstable. It passes when run with only > packages from testing. In tabular form:
Thanks for the bug report. > t/70future-io.t .............. ok 1 - Future::IO->sleep took at least 1.5 > ok 2 - Future::IO->sleep took no more than 4 > ok 3 - Future::IO->sysread > Nothing was ready after 10 second wait; called at > /usr/share/perl5/IO/Async/Test.pm line 214 > # Tests were run but no plan was declared and done_testing() was not seen. > # Looks like your test exited with 255 just after 3. > Dubious, test returned 255 (wstat 65280, 0xff00) > All 3 subtests passed > Test Summary Report > ------------------- > t/70future-io.t (Wstat: 65280 Tests: 3 Failed: 0) > Non-zero exit status: 255 > Parse errors: No plan found in TAP output > Files=63, Tests=1638, 105 wallclock secs ( 0.30 usr 0.09 sys + 8.33 cusr > 1.42 csys = 10.14 CPU) So some kind of timeout … Whatever the reason is, it's not the update from 0.800 to 0.801, as the whole diff (modulo versions numbers etc.) is: #v+ --- a/Changes +++ b/Changes @@ -1,5 +1,9 @@ Revision history for IO-Async +0.801 2021-12-15 + [BUGFIXES] + * Remove extraneous test-time use of Data::Dump (RT140143) + 0.800 2021-11-11 [CHANGES] * Bumped up to three-digit minor version number --- a/t/50resolver.t +++ b/t/50resolver.t @@ -308,8 +308,6 @@ my @expect_passive_3000 = ( my @got = @{$result}[1..$#$result]; - use Data::Dump 'pp'; - is_deeply( @got, @expect_lo_80, '$resolver->getaddrinfo resolved addresses synchronously' ); undef $result; @@ -344,8 +342,7 @@ my @expect_passive_3000 = ( my @got = @{$result}[1..$#$result]; - is_deeply( @got, @expect_passive_3000, '$resolver->getaddrinfo passive - resolved addresses' ) or - diag( "Got=", pp(@got), "; expected=", pp(@expect_passive_3000) ); + is_deeply( @got, @expect_passive_3000, '$resolver->getaddrinfo passive - resolved addresses' ); } { #v- Looking at https://ci.debian.net/packages/libi/libio-async-perl/testing/ppc64el/ I notice that the tests for 0.800-2 also failed. Not sure if this good or bad :) Ah, in 0.800-2 we have: libio-async-perl (0.800-2) unstable; urgency=medium * Don't skip any tests, as Test::Future::IO::Impl is in Debian. * Add test dependency on libfuture-io-perl. and t/70future-io.t was skipped in 8.800-1. So t/70future-io.t fails consistently since it is run (0.800-2 and 0.801-1). But only on ppc64el. 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 VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- NP: Alan Jackson: Chattahoochee
signature.asc
Description: Digital Signature
Read more here: Source link