Skip Menu |
 

This queue is for tickets about the Test-Harness CPAN distribution.

Report information
The Basics
Id: 77730
Status: resolved
Priority: 0/
Queue: Test-Harness

People
Owner: Nobody in particular
Requestors: 'spro^^*%*^6ut# [...] &$%*c
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: 3.23
Fixed in: 3.29



Subject: Reason for load failure not given
Download (untitled) / with headers
text/plain 909b
If TAP::Formatter::Console cannot be loaded for whatever reason, then I get this error when trying to run perl’s tests through Test::Harness: Can't load TAP::Formatter::Console at harness line 231. The piece of code in ‘harness’ that triggers this error is: my $h = TAP::Harness->new({ rules => $rules, color => $color, jobs => $jobs, verbosity => $Verbose, exec => sub { my ($harness, $test) = @_; my $options = $options{$test}; if (!defined $options) { $options = $options{$test} = _scan_test($test, $type); } return [ split ' ', _cmd($options, $type) ]; }, }); So TAP::Harness->new, or something it calls, is dying. But it doesn’t tell me why the formatter cannot load. Could this be changed to include $@ in its output as well? After all, dying with a separate message would cause $@ to be clobbered with the new message.
On Sat Jun 09 00:32:52 2012, SPROUT wrote: Show quoted text
> If TAP::Formatter::Console cannot be loaded for whatever reason, then > I get this error when > trying to run perl’s tests through Test::Harness: > > Can't load TAP::Formatter::Console at harness line 231. > > The piece of code in ‘harness’ that triggers this error is: > > > my $h = TAP::Harness->new({ > rules => $rules, > color => $color, > jobs => $jobs, > verbosity => $Verbose, > exec => sub { > my ($harness, $test) = @_; > > my $options = $options{$test}; > if (!defined $options) { > $options = $options{$test} = _scan_test($test, $type); > } > > return [ split ' ', _cmd($options, $type) ]; > }, > }); > > So TAP::Harness->new, or something it calls, is dying. But it doesn’t > tell me why the > formatter cannot load. > > Could this be changed to include $@ in its output as well? After all, > dying with a separate > message would cause $@ to be clobbered with the new message.
I just pushed a patch fixing this, it will be part of the upcoming 3.29 release. Leon


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.