I retract the previous comment. It was based on the file sent by Ovid; when
I run make spectest myself, I get more informative output.  In my case, 2 of
the declaration-order tests are what's failing:

Failed Test                          Stat Wstat Total Fail  List of Failed
------------------------------------------------------------------------------------------------------------------------------------------------------------
t/spec/S12-class/declaration-order.t    0     6     2    0  ??
1490 subtests skipped.

Failed 1/219 test scripts. 0/6484 subtests failed.
Files=219, Tests=6484, 1224 wallclock secs (661.02 cusr + 28.94 csys =
689.96 CPU)



On Thu, Nov 13, 2008 at 6:03 PM, Mark J. Reed <[EMAIL PROTECTED]> wrote:

> On Thu, Nov 13, 2008 at 5:31 PM, Ovid <
> [EMAIL PROTECTED]> wrote:
>
>> Now this test passes (r32629), but the Perl 6 test suite is still failing.
>>  Now, however, I can't tell which test fails.
>
>
> Seems like the summary report should at least include counts of passed vs
> failed tests.  I assume the result of "FAIL" means that at least one of the
> 6,487 tests failed, but that's not very informative... but I can't even find
> the code that generates this output to try and fix it:
>
> Test Summary Report
> -------------------
> Files=220, Tests=6487, 304 wallclock secs ( 1.65 usr  0.82 sys + 539.47 cusr 
> 22.60 csys = 564.54 CPU)
> Result: FAIL
>
> It would also help if the actual test output weren't overrun with "Use of
> uninitialized value".  Is that the result of bad tests or bad harness?
>
> --
> Mark J. Reed <[EMAIL PROTECTED]>
>
>


-- 
Mark J. Reed <[EMAIL PROTECTED]>

Reply via email to