Threading or (pseudo-)forking? (It kinda looks like you have two threads running the tests simultaneously.) Or just confused test numbers?
Either way, you are getting the same test numbers twice in the test stream:
... ok n ok n ok n+1 ok n+1 ...
I ran into this a lot when writing tests that fork. Mostly I resolved it by manually increasing the test count and waiting for the children to terminate:
# in the parent, while a child is running $n tests: my $Test = Test::More->builder; $Test->current_test( $Test->current_test + $n ); wait;
Could we perchance see the .t code that produces these complaints?
Update: As andreas1234567's code demonstrates, the error message does not mean what I thought it meant (and still think it says). An "ok 2" followed by an "ok 1" will produce "test 2 answered after test 2". (And an "ok 1" followed by another "ok 1" are quietly accepted as two different tests. Bah.)
Oh well, it's still a case of test numbers coming in the wrong order. (And meanwhile, a new harness is on its way ...)
print "Just another Perl ${\(trickster and hacker)},"
The Sidhekin proves Sidhe did it!
In reply to Re: Odd output from Test::More
by Sidhekin
in thread Odd output from Test::More
by Bloodnok
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |