On Nd 15 Maj 2016, 10:45:04, SREZIC wrote:
Show quoted text> On 2016-05-09 07:54:03, STARLIGHT wrote:
> > We tried to reproduce the issue on a fresh install to no avail. It is
> > being investigated in 0.4_01 dev release.
>
> Problem seems to be that the tests use the first prove in $ENV{PATH},
> which may belong to a different perl than the one used in tests. In
> this case the tests usually fail (because the system perl does not
> have the deps installed etc.)
>
> A solution could look like this:
>
> diff --git a/t/20-single.t b/t/20-single.t
> index bf9bc62..618554a 100755
> --- a/t/20-single.t
> +++ b/t/20-single.t
> @@ -25,7 +25,7 @@ foreach my $test (@tests) {
> my $test_output = File::Temp->new();
>
> local $ENV{TAP_FORMATTER_BAMBOO_OUTFILE}=$test_output;
> - system("prove -b --formatter=TAP::Formatter::Bamboo $test >$f_out
> 2>$f_err");
> + system("$^X -S prove -b --formatter=TAP::Formatter::Bamboo $test
> >$f_out 2>$f_err");
>
> my $err = $?;
>
>
> Another solution is to look into %Config for possible script locations
> (scriptdir, maybe also installsitescript), and search there for
> "prove".
Thanks! Indeed, we thought that including Test::Harness would cause its installed "prove" to be used. I'll build another dev release to test the patch. Thank you very much for interest and for pointing out the %Config hash, didn't know about it.
best,
StarLight