Derby nightly testrun was killed and is disable (was Re: zero failures on jdk 1.6)

["David W. Van Couvering" <Da...@Sun.COM>]

One of our QA guys in Norway (Bjorn) killed a Derby test run last night 
as we were running out of disk space (I saw an email to this effect on 
an internal list).

It's Easter holiday in Norway and most everybody's away for the rest of 
the week...  I talked to him this morning and he isn't sure *what* Derby 
test he killed, but he has now disabled the night tests until everyone 
gets back.

So I'm not sure of the validity of this jdk16 test run...

Thanks,

David

Rick Hillegas wrote:
> This is good news. I think we're ready now to wire the jdbc40 suite into 
> derbyall (it should only run on jdk16).
> 
> BTW, my last derbyall on jdk14 reported that it ran 645 tests.
> 
> Regards,
> -Rick
> 
> Andrew McIntyre wrote:
> 
>> On 4/12/06, Ole.Solberg@sun.com <Ol...@sun.com> wrote:
>>  
>>
>>> *Derby* 393268/2006-04-11 19:45:56 CEST
>>> *derbyall*
>>>
>>> Failed  Tests    OK  Skip  Duration       Platform
>>> -------------------------------------------------------
>>> *Jvm: 1.6*
>>>    0    647    647     0   100.00%     SunOS-5.10_i86pc-i386
>>>   
>>
>>
>> Hey - zero failures on jdk 1.6! Yay!
>>
>> One thing though - the number of tests run is incorrect. If you tally
>> up the total tests run from the individual suites, you get 776, not
>> 647. I guess the harness has forgotten how to count? ;-)
>>
>> Actually, I think its not counting the number of tests in the nist
>> suite or something - the difference (129) is suspiciously close to the
>> number of tests in the nist suite, and the nist suite is the only one
>> that runs with useprocess=false...
>>
>> andrew
>>  
>>
>