Ovid wrote:
> Basically, if I fork a child, when we return, Test::Builder will not have the 
> new test count, so I explicitly use shared memory [1].  While the above runs 
> just fine with prove, runtests (from the TAP::Parser distribution), fails 
> with the following:
> 
>   ok 1 - mytest called
>   ok 2 - in the child
>   ok 3  - in the parent
>   1..3
>    All 3 subtests passed 
> 
>   Test Summary Report
>   -------------------
>   forkingtest.pl (Wstat: 0 Tests: 3 Failed: 0)
>     Parse errors: No plan found in TAP output
>   Files=1, Tests=3,  0 wallclock secs ( 0.05 cusr +  0.02 csys =  0.07 CPU)

Interestingly runtests is happy for me:

[13:38] andy $ runtests -v forkingtest.pl
forkingtest.......ok 1 - mytest called
ok 2 - in the child
ok 3  - in the parent
1..3
 All 3 subtests passed

Test Summary Report
-------------------
forkingtest.pl (Wstat: 0 Tests: 3 Failed: 0)
  Parse errors: No plan found in TAP output
Files=1, Tests=3,  0 wallclock secs ( 0.03 cusr +  0.02 csys =  0.05 CPU)

Want to compare versions of things? I'm assuming we're running the same
version of runtests + TAP::Parser :)

-- 
Andy Armstrong, Hexten

Reply via email to