On Fri, 20 Jan 2017 09:16:18 -0800, mt1...@gmail.com wrote: > Hi Will, > > How can it happen that a test gets hurt in this way? If I know this I > could better search for the problem. > > Regards, > Marcel
Hi, Here's how that error happens: The TAP protocol[^1] expects tests to be numbered and (as seen in your output) the test harness will complain if it spots tests missing or not in order. So if your tests produce junk output (that is something other than stuff produced by Test.pm6's routines), it could confuse the harness by making it interpret junk output as a test. Another harder way to accomplishing that is to run the tests in multiple threads, to trigger a data race in the Test.pm6's internal test counter and make it output wrong stuff. Yet another way is to use a buggy test harness that fails to recognize a test and so thinks something's missing. We had such a bug recently, though it got introduced on Jan 2nd and got fixed[^2] on Jan 5th. From your version, I see you're running Rakudo from some time in October, so this probably isn't it... I'd suggest you try using a release version of Rakudo or HEAD. I tried running that test on my box, but instead of TAP output it seems to be just producing time-stamped connection failures. [1] https://testanything.org/ [2] https://github.com/rakudo/rakudo/commit/b120ac401a0795f5f4c5fcd6e775848b4b755508
