note Sidhekin 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: <c> ... ok n ok n ok n+1 ok n+1 ... </c> 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: <c> # in the parent, while a child is running $n tests: my $Test = Test::More->builder; $Test->current_test( $Test->current_test + $n ); wait; </c> 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 <c>"ok 2"</c> followed by an <c>"ok 1"</c> will produce <c>"test 2 answered after test 2"</c>. (And an <c>"ok 1"</c> followed by another <c>"ok 1"</c> 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 ...) <div class="pmsig"><div class="pmsig-106949"> <code>print "Just another Perl ${\(trickster and hacker)},"</code> The Sidhekin proves Sidhe did it! </div></div> 641197 641197