On 14 Nov 2007, at 23:11, Andy Dougherty wrote:
That's a Test::Harness 3 change. It doesn't understand the
#!./parrot
lines at the top of some of the tests.
It's actually Perl that handles the ./parrot shebang. Test::Harness
just asks Perl to run the test.
It looks as if ./parrot doesn't like the -I switches. But that's odd
because Test::Harness 2.64 passed them too.
I've just done a little experiment. Here's my test:
[02:16] andy $ cat parrot.t
#!./parrot
... does nothing ...
Here's my (rather minimal) Parrot implementation:
[02:16] andy $ cat ./parrot
#!/alt/local/bin/perl
warn "# ", join(' ', @ARGV), "\n";
print "1..1\nok 1\n";
Here's what it says with Test::Harness 2.64:
[02:16] andy $ perl -Ireference/Test-Harness-2.64/lib reference/Test-
Harness-2.64/bin/prove -vb parrot.t
parrot....# -Iblib/arch -Iblib/lib parrot.t
1..1
ok 1
ok
All tests successful.
Files=1, Tests=1, 0 wallclock secs ( 0.00 cusr + 0.00 csys = 0.00
CPU)
And here with Test::Harness 3.01:
[02:16] andy $ prove -vb parrot.t
parrot......
1..1
ok 1
# -I/Users/andy/Works/Perl/TAPx-Parser/tapx/trunk/blib/lib -I/Users/
andy/Works/Perl/TAPx-Parser/tapx/trunk/blib/arch parrot.t
ok
All tests successful.
Files=1, Tests=1, 0 wallclock secs ( 0.01 usr + 0.00 sys = 0.01 CPU)
Result: PASS
The only difference seems to be that T::H 3.01 makes the paths absolute.
If I get time tomorrow I'll install parrot on this machine and try it
for real.
--
Andy Armstrong, Hexten
