Bug #131884 for DNS-BL: POD tests fail (missing =encoding)

Wed Feb 19 18:01:43 2020 SREZIC [...] cpan.org - Ticket created

Subject:

POD tests fail (missing =encoding)

On my smoker systems: ... PERL_DL_NONLAZY=1 "/opt/perl-5.30.1/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(0, 'blib/lib', 'blib/arch')" t/*.t # Failed test 'POD test for /home/cpansand/.cpan/build/2020022000/DNS-BL-0.03-0/blib/lib/DNS/BL.pm' # at t/00-load.t line 45. # /home/cpansand/.cpan/build/2020022000/DNS-BL-0.03-0/blib/lib/DNS/BL.pm (354): Non-ASCII character seen before =encoding in 'Mu�oz,'. Assuming CP1252 # Failed test 'POD test for /home/cpansand/.cpan/build/2020022000/DNS-BL-0.03-0/blib/lib/DNS/BL/Entry.pm' # at t/00-load.t line 45. # /home/cpansand/.cpan/build/2020022000/DNS-BL-0.03-0/blib/lib/DNS/BL/Entry.pm (150): Non-ASCII character seen before =encoding in 'Mu�oz,'. Assuming CP1252 ... Probably an =encoding directive is missing.

Thu Feb 20 00:00:15 2020 ether [...] cpan.org - Correspondence added

While this test failure is indeed an issue that should be corrected, please don't allow pod, critic, coverage or kwalitee tests to run for normal user installs, as they make the installation fail unnecessarily when newer versions of the tester module introduces errors that you cannot anticipate. Also spelling tests are dependent on what dictionaries are installed locally, and critic tests use all plugins that are installed, neither of which can be predicted in advance. Either move these tests to xt/, or guard them with: plan skip_all => "These tests are for authors only!" unless $ENV{AUTHOR_TESTING} or $ENV{RELEASE_TESTING};

Thu Feb 20 00:00:15 2020 The RT System itself - Status changed from 'new' to 'open'