-=| gregor herrmann, 27.06.2014 21:44:36 +0200 |=- > Control: tag -1 + confirmed > > On Fri, 27 Jun 2014 21:51:25 +0300, Niko Tyni wrote: > > > # Failed test 'Pod coverage on DhMakePerl::Config' > > # at t/pod-coverage.t line 26. > > # Coverage for DhMakePerl::Config is 71.4%, with 2 naked subroutines: > > # commands > > # options > > # Looks like you failed 1 test of 24. > > t/pod-coverage.t .................... > > Dubious, test returned 1 (wstat 256, 0x100) > > Failed 1/24 subtests > > (less 2 skipped subtests: 21 okay) > > t/pod.t ............................. ok > > t/rules.t ........................... ok > > t/split_version_relation.t .......... ok > > > > Test Summary Report > > ------------------- > > t/pod-coverage.t (Wstat: 256 Tests: 24 Failed: 1) > > Failed test: 8 > > Non-zero exit status: 1 > > Files=22, Tests=408, 21 wallclock secs ( 0.19 usr 0.01 sys + 17.93 cusr > > 1.28 csys = 19.41 CPU) > > Result: FAIL > > Interesting that POD coverage changes. > > Even more interesting is that "commands" and "options" are no subs > but constants. -- Not sure what do do here ... Except for declaring > them private but this seems a bit silly:
Thanks for looking into this. I'd document the "constants" in the POD, but the general fix is to skip POD-related tests unless in a special environment. I'll try to find what was the latest recommendation about the name of the environment variable. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
