+++ This bug was initially created as a clone of Bug #1091376 +++

Description of problem:
Spurious warnings in test runs, e.g.

$ ./Build test
# Testing Test::ConsistentVersion 0.2.3
t/00.load.t ....... ok
t/01.good.t ....... ok
t/02.bad.t ........ ok
t/perlcritic.t .... ok
Use of uninitialized value in split at /usr/share/perl5/vendor_perl/TAP/Parser/SourceHandler/Perl.pm line 170.
t/pod-coverage.t .. ok
Use of uninitialized value in split at /usr/share/perl5/vendor_perl/TAP/Parser/SourceHandler/Perl.pm line 170.
t/pod.t ........... ok
# Distribution version: 0.2.3
t/version.t ....... ok
All tests successful.
Files=7, Tests=12,  2 wallclock secs ( 0.03 usr  0.01 sys +  1.19 cusr  0.07 csys =  1.30 CPU)
Result: PASS

Version-Release number of selected component (if applicable):
perl-Test-Harness-3.28-2.el7


This is CPAN RT#85106 and was fixed upstream in version 3.29. There's an API change there though, which probably makes an update unsuitable for RHEL. The fix should easily enough be backported to 3.28 though.

[...]
--- Additional comment from Petr Pisar on 2014-04-28 09:15:10 GMT ---

How to test:

(1) Install perl-Test-Harness.

(2) Create test file `tainted.t' with tainted mode:
$ cat tainted.t 
#!perl -T
print "1..0 # SKIP foo\n";

(3) Run `prove tainted.t'.
Before:
  A warning about an uninitialized value is printed on standard error output:
$ prove tainted.t
Use of uninitialized value in split at /usr/share/perl5/vendor_perl/TAP/Parser/SourceHandler/Perl.pm line 170.
tainted.t .. skipped: foo
Files=1, Tests=0,  0 wallclock secs ( 0.03 usr +  0.01 sys =  0.04 CPU)
Result: NOTESTS

After:
  No warning on standard error output is printed:
$ prove tainted.t 
tainted.t .. skipped: foo
Files=1, Tests=0,  0 wallclock secs ( 0.03 usr +  0.01 sys =  0.04 CPU)
Result: NOTESTS

--- Additional comment from Petr Pisar on 2014-04-28 09:16:18 GMT ---

F20 (perl-Test-Harness-3.28-3.fc20.noarch) is affected.