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
On 01/20/2017 05:24 PM, Will Coleda via RT wrote:
On Fri, 20 Jan 2017 06:09:00 -0800, mt1...@gmail.com wrote:
Hi,
Since using Log::Async in MongoDB I get problems while testing. All
tests run ok but at the end the Test returns failure
...
ok 6 - Testing explain and performance using hint
2017-01-20 13:04:40.783616 [I] 1: Test
/home/travis/build/MARTIMM/mongo-perl6-driver/t/450-find.t stop
1..6
Failed 3/6 subtests
... other test programs ... Test Summary Report
-------------------
t/450-find.t (Wstat: 0 Tests: 3 Failed: 0)
Parse errors: Tests out of sequence. Found (3) but expected (1)
Tests out of sequence. Found (5) but expected (2)
Tests out of sequence. Found (6) but expected (3)
Bad plan. You planned 6 tests but ran 3.
Files=11, Tests=42, 228 wallclock secs ( 0.14 usr 0.02 sys + 208.76 cusr
9.47 csys = 218.39 CPU)
Result: FAIL
You can see complete report on Travis-ci at
https://travis-ci.org/MARTIMM/mongo-perl6-driver.
This is Rakudo version 2016.10-239-g0cf7b36 built on MoarVM version
2016.10-43-gb4cd2a6
implementing Perl 6.c.
Marcel
This is a failure on an ecosystem module, not core rakudo.
Unless there's an example of how this is explicitly a rakudo bug, this should
be reported on https://github.com/MARTIMM/mongo-perl6-driver/issues
Regards.
