Bug #115137 for Youri-Config: t/kwalitee.t fails (meta yml problem)

Tue Jun 07 02:56:16 2016 SREZIC [...] cpan.org - Ticket created

Subject:

t/kwalitee.t fails (meta yml problem)

See subject. Test output looks like this: ... PERL_DL_NONLAZY=1 "/usr/perl5.22.1p/bin/perl5.22.1" "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(0, 'blib/lib', 'blib/arch')" t/*.t These tests should not be running unless AUTHOR_TESTING=1 and/or RELEASE_TESTING=1! # Failed test 'meta_yml_conforms_to_known_spec' # at t/kwalitee.t line 7. # Error: META.yml does not conform to any recognised META.yml Spec. # Details: # Missing mandatory field, 'abstract' (abstract) [Validation: 1.4];value is an undefined string (abstract) [Validation: 1.4] # Missing mandatory field, 'abstract' (abstract) [Validation: 1.4];value is an undefined string (abstract) [Validation: 1.4] # Remedy: Take a look at the META.yml Spec at http://module-build.sourceforge.net/META-spec-v1.4.html (for version 1.4) or http://search.cpan.org/perldoc?CPAN::Meta::Spec (for version 2), and change your META.yml accordingly. # Looks like you failed 1 test of 17. t/kwalitee.t ...... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/17 subtests ...

Tue Jun 07 19:13:56 2016 ether [...] cpan.org - Correspondence added

On 2016-06-06 23:56:16, SREZIC wrote: Show quoted text

> See subject. Test output looks like this: > > ... > PERL_DL_NONLAZY=1 "/usr/perl5.22.1p/bin/perl5.22.1" "- > MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef > *Test::Harness::Switches; test_harness(0, 'blib/lib', 'blib/arch')" > t/*.t > These tests should not be running unless AUTHOR_TESTING=1 and/or > RELEASE_TESTING=1!

While this test failure is indeed an issue that should be corrected, note the output of the test above -- please don't allow pod, critic 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, both of which cannot be predicted in advance. Either move them to xt/, or guard them with: plan skip_all => "These tests are for authors only!" unless $ENV{AUTHOR_TESTING} or $ENV{RELEASE_TESTING};

Tue Jun 07 19:13:56 2016 The RT System itself - Status changed from 'new' to 'open'