Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse-dev] [eclipse-build]Build I20030709 (Timestamp: 200307090800):Automated JUnit Testing complete. Test failures/errors occurred.


The deadlock has reoccured in I20030710.

Sonia



John Arthorne/Ottawa/IBM@IBMCA
Sent by: eclipse-dev-admin@xxxxxxxxxxx

07/09/2003 05:15 PM
Please respond to eclipse-dev

       
        To:        eclipse-dev@xxxxxxxxxxx
        cc:        
        Subject:        Re: [eclipse-dev] [eclipse-build]Build I20030709 (Timestamp:  200307090800):Automated JUnit Testing complete.  Test failures/errors occurred.




I have investigated this deadlock problem but from the stack trace it appears that one thread has traversed an impossible code path.  It is consistently reproducible on one VM version, but not reproducible at all on any other versions, so I suspect a VM or JIT bug.  Although I can easily recreate the test scenario in a debugger, I cannot make it go down the invalid code path.  I have made some minor changes in the code to try to "fool" the compiler into not optimizing the snippet in question (I've made a field accessed by two threads volatile to avoid thread local caching).  We'll see if this does the trick for tomorrow's rebuild.


Also, since the deadlock occurred in label decoration, it's possible that it was brought on by a bug that caused overly eager decoration (bug
39825).  This bug has been fixed for tomorrow's build, so it might make the problem go away.



Darin Wright/Ottawa/IBM@IBMCA
Sent by: eclipse-dev-admin@xxxxxxxxxxx

07/09/2003 12:06 PM
Please respond to eclipse-dev

       
       To:        eclipse-dev@xxxxxxxxxxx

       cc:        

       Subject:        Re: [eclipse-dev] [eclipse-build]Build I20030709 (Timestamp:  200307090800):Automated JUnit Testing complete.  Test failures/errors occurred.





I downloaded the build and test harness, and ran without any errors (see attached result.xml). However the log you have provided shows a deadlock between a "worker" thread the "main" thread.
 

Could core please take a look at this to see if it may be a problem with the job manager/decoration support.


Thanks,


Darin



Sonia Dimitrov/Ottawa/IBM@IBMCA
Sent by: eclipse-dev-admin@xxxxxxxxxxx


07/09/2003 10:29 AM

Please respond to eclipse-dev
         
       To:        eclipse-dev@xxxxxxxxxxx

       cc:        

       Subject:        Re: [eclipse-dev] [eclipse-build]Build I20030709 (Timestamp:  200307090800):Automated JUnit Testing complete.  Test failures/errors occurred.
 





I reran the Ant tests and encountered the same problem.  I have attached the thread dump.
 

Sonia
 




Sonia Dimitrov/Ottawa/IBM@IBMCA  
Sent by: eclipse-dev-admin@xxxxxxxxxxx
 

07/09/2003 10:52 AM
 
Please respond to eclipse-dev
 
         
       To:        eclipse-dev@xxxxxxxxxxx
 
       cc:        
 
       Subject:        [eclipse-dev] [eclipse-build]Build I20030709 (Timestamp:  200307090800):Automated JUnit Testing complete.  Test failures/errors occurred.




Build I20030709 (Timestamp: 200307090800):  Automated JUnit testing is complete.  Test failures/errors occurred in the following:  


org.eclipse.ant.tests.core_win32

org.eclipse.jdt.debug.tests_linux.motif

org.eclipse.releng.tests_linux.motif

org.eclipse.releng.tests_win32


http://download.eclipse.org/downloads/drops/I-I20030709-200307090800/testResults.php

_______________________________________________

eclipse-dev mailing list

eclipse-dev@xxxxxxxxxxx

http://dev.eclipse.org/mailman/listinfo/eclipse-dev

 



#### stack.txt has been removed from this note on July 09, 2003 by Darin Wright





#### org.eclipse.ant.tests.core_.xml has been removed from this note on July 09, 2003 by John Arthorne


Back to the top