db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Matrigali <mikem_...@sbcglobal.net>
Subject Re: [jira] Commented: (DERBY-3555) Hang forever while trying to run "ant junitreport"
Date Wed, 19 Mar 2008 20:36:36 GMT
Daniel John Debrunner (JIRA) wrote:
>     [ https://issues.apache.org/jira/browse/DERBY-3555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12580503#action_12580503
> Daniel John Debrunner commented on DERBY-3555:
> ----------------------------------------------
> Possibly due to DERBY-3544??

I will try out the DERBY-3544 patch and post whether it helps or not.

>> Hang forever while trying to run "ant junitreport"
>> --------------------------------------------------
>>                 Key: DERBY-3555
>>                 URL: https://issues.apache.org/jira/browse/DERBY-3555
>>             Project: Derby
>>          Issue Type: Bug
>>          Components: Regression Test Failure
>>    Affects Versions:
>>         Environment: sane classes built off of trunk on a windows XP machine with
4 processors, running ibm16 jvm.
>> java version "1.6.0"
>> Java(TM) SE Runtime Environment (build pwi3260sr1-20080309_01)
>> IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260-20080308
>> _17822 (JIT enabled, AOT enabled)
>> J9VM - 20080308_017822_lHdSMr
>> JIT  - r9_20080307_1821
>> GC   - 20080305_AB)
>> JCL  - 20080301_01
>>            Reporter: Mike Matrigali
>>         Attachments: junit_20080319_1111.zip
>> Running "ant junit report" has consistently hung forever in this configuration (I
think I have tried about 4 times on various latest builds off of the trunk".  The latest try
was against build 638425.  I will attach a zip of the junit report information.  On windows
I could only get the stack trace from the ant control jvm, not sure how to get the actual
test jvm to dump javacore to see what is going on there.  I have been able to consistently
run "ant junitreport" against the trunk and ibm15 jvm, this is the first time on this machine
I have tried running the tests this way against ibm16.  
>> I will also try going back to the direct runner separate from ant to see if maybe
the hang is ant related.  In the old harness I have seen timing issues with the control and
child jvm getting out of sync.  

View raw message