Subject: | Test-Kwalitee-Extra fails two tests with perl-5.29.8 |
Date: | Sat, 23 Feb 2019 10:05:10 -0500 |
To: | bug-Test-Kwalitee-Extra [...] rt.cpan.org, Chad Granum <exodist7 [...] gmail.com> |
From: | James E Keenan <jkeenan [...] pobox.com> |
In the course of testing the 'CPAN River 3000' against the latest perl 5
monthly development release, I encountered these test failures:
#####
{
author => "YAKEX",
dist => "Test-Kwalitee-Extra",
distname => "Test-Kwalitee-Extra-v0.4.0",
distversion => "v0.4.0",
grade => "FAIL",
prereqs => undef,
test_output => [
"Building and testing Test-Kwalitee-Extra-v0.4.0",
"cp lib/Test/Kwalitee/Extra.pm blib/lib/Test/Kwalitee/Extra.pm",
"PERL_DL_NONLAZY=1
\"/usr/home/jkeenan/var/tad/testing/perl-5.29.8/bin/perl\"
\"-MExtUtils::Command::MM\" \"-MTest::Harness\" \"-e\" \"undef
*Test::Harness::Switches; test_harness(0, 'blib/lib', 'blib/arch')\" t/*.t",
"t/00-compile.t .................... ok",
"t/01-kwalitee.t ................... ok",
"t/02-exclude-class.t .............. ok",
"t/03-include.t .................... ok",
"t/04-prereq_maches_use.t .......... ok",
"",
"# Failed test 'expected failure of build_prereq_matches_use'",
"# at t/05-build_prereq_matches_use.t line 35.",
"# STDOUT is:",
"# > ok 1 - build_prereq_matches_use by Test::Kwalitee::Extra",
"# not:",
"# > not ok 1 - build_prereq_matches_use by Test::Kwalitee::Extra",
"# as expected",
"# STDERR is:",
"# > ",
"# > ",
"# > ",
"# > ",
"# not:",
"# > /#\\s+Failed\\ test.*?\\n?.*?at\\
t\\/05\\-build_prereq_matches_use\\.t line 33.*\\n?/",
"# > # Detail: This distribution uses a module or a dist in its
test suite that's not listed as a build prerequisite.",
"# > # Detail: Missing: Pod::Coverage::TrustPod in
Pod-Coverage-TrustPod, Test::Pod in Test-Pod, Test::Pod::Coverage in
Test-Pod-Coverage",
"# > # Remedy: List all modules used in the test suite in
META.yml build_requires",
"# as expected",
"t/05-build_prereq_matches_use.t ... ",
"Failed 1/1 subtests ",
"",
"# Failed test 'expected failure of build_prereq_matches_use'",
"# at t/06-minperlver.t line 29.",
"# STDOUT is:",
"# > ok 1 - build_prereq_matches_use by Test::Kwalitee::Extra",
"# not:",
"# > not ok 1 - build_prereq_matches_use by Test::Kwalitee::Extra",
"# as expected",
"# STDERR is:",
"# > ",
"# > ",
"# > ",
"# > ",
"# not:",
"# > /#\\s+Failed\\ test.*?\\n?.*?at\\ t\\/06\\-minperlver\\.t line
27.*\\n?/",
"# > # Detail: This distribution uses a module or a dist in its
test suite that's not listed as a build prerequisite.",
"# > # Detail: Missing: File::Spec::Functions in PathTools,
Pod::Coverage::TrustPod in Pod-Coverage-TrustPod, Term::ANSIColor in
Term-ANSIColor, Test::Pod in Test-Pod, Test::Pod::Coverage in
Test-Pod-Coverage",
"# > # Remedy: List all modules used in the test suite in
META.yml build_requires",
"# as expected",
"t/06-minperlver.t ................. ",
"Failed 1/1 subtests ",
"t/08-_get_packages_not_indexed.t .. ok",
"t/09-_count_tests.t ............... ok",
"t/author-critic.t ................. skipped: these tests are for
testing by the author",
"t/author-pod-coverage.t ........... skipped: these tests are for
testing by the author",
"t/author-pod-syntax.t ............. skipped: these tests are for
testing by the author",
"",
"Test Summary Report",
"-------------------",
"t/05-build_prereq_matches_use.t (Wstat: 0 Tests: 1 Failed: 1)",
" Failed test: 1",
"t/06-minperlver.t (Wstat: 0 Tests: 1 Failed: 1)",
" Failed test: 1",
"Files=12, Tests=64, 22 wallclock secs ( 0.04 usr 0.02 sys + 4.84
cusr 1.67 csys = 6.56 CPU)",
"Result: FAIL",
],
via => "App::cpanminus::reporter 0.17 (1.7044)",
}
#####
The failure in t/06-minperlver.t appears to be intermittent, but it was
originally reported in 2015 in
https://rt.cpan.org/Ticket/Display.html?id=104113.
The failures in t/05-build_prereq_matches_use.t are new. These failures
were observed on both FreeBSD-11.1 and Linux. This test relies upon
Test::Builder::Tester, which is part of the Test-Simple distribution.
That distribution is shipped with the Perl 5 core distribution and the
version shipped with core was upgraded during the past month. You may
wish to communicate with the people maintaining Test-Simple to see
whether the STDOUT and STDERR for which you are testing needs modification.
Thank you very much.
Jim Keenan