I decided to update my DateTime::Calendar::Discordian but the CPAN Testers are reporting lots of failures with the new version like e.g. this:

t/04-perl-critic.....................Can't locate Test/Perl/Critic.pm 
+in
@INC (@INC contains:
/usr/home/david/cpantesting/perl-5.10.0/.cpan/build/DateTime-Calendar-
+Disc
ordian-0.9.5-R6NHvJ/blib/lib
/usr/home/david/cpantesting/perl-5.10.0/.cpan/build/DateTime-Calendar-
+Disc
ordian-0.9.5-R6NHvJ/blib/arch
/home/david/cpantesting/perl-5.10.0/lib/5.10.0/i386-freebsd-thread-mul
+ti
/home/david/cpantesting/perl-5.10.0/lib/5.10.0/i386-freebsd-thread-mul
+ti
/home/david/cpantesting/perl-5.10.0/lib/5.10.0
/home/david/cpantesting/perl-5.10.0/lib/site_perl/5.10.0/i386-freebsd-
+thre
ad-multi
/home/david/cpantesting/perl-5.10.0/lib/site_perl/5.10.0/i386-freebsd-
+thre
ad-multi /home/david/cpantesting/perl-5.10.0/lib/site_perl/5.10.0 .
/home/david/cpantesting/perl-5.10.0/lib/5.10.0/i386-freebsd-thread-mul
+ti
/home/david/cpantesting/perl-5.10.0/lib/5.10.0
/home/david/cpantesting/perl-5.10.0/lib/site_perl/5.10.0/i386-freebsd-
+thre
ad-multi /home/david/cpantesting/perl-5.10.0/lib/site_perl/5.10.0 .) a
+t
t/04-perl-critic.t line 14.
BEGIN failed--compilation aborted at t/04-perl-critic.t line 14.
# Looks like your test died before it could output anything.
dubious
[download]

...on lots of different perl versions and OS's.

The failing test looks like this:

use strict;
use warnings;
use English qw(-no_match_vars);
use Test::More;

if ( not $ENV{TEST_AUTHOR} ) {
    my $msg = 'Author test.  Set $ENV{TEST_AUTHOR} to a true value to 
+run.';
    plan( skip_all => $msg );
}

eval { use Test::Perl::Critic (-profile => 't/perlcriticrc'); };

if ( $EVAL_ERROR ) {
    my $msg = 'Test::Perl::Critic required to criticise code';
    plan( skip_all => $msg );
}

all_critic_ok()
[download]

What gives? The eval should catch if Test::Perl::Critic is not installed right?

I am using a similar idiom for tests using Test::Pod and Test::Pod::Coverage and they aren't causing problems.