[jboss-dev] current testsuite results

[Brian Stansberry]

Brian Stansberry wrote:
> Dimitris Andreadis wrote:
>> At this point it seems we are left with jboss messaging and clustering 
>> failures, timing issues and leaks that come and go.
>>
>> The most persisting ones are the BaseConnectionManagerUnitTestCase in 
>> the jrockit run and the FieldGranularityClassloaderLeakUnitTestCase in 
>> the sun builds and the AopPreparedClassesClassloaderLeakUnitTestCase 
>> in the sun15-sun16 report.
>>
> 
> I'm working on disabling the clustered classloader leak tests on Sun vm. 
> If they fail on jrockit that's enough to tell us we have a problem.
> 

The following has been added to set an ant property if the VM vendor is 
Sun; property can be used in ant if/unless attributes to enable/disable 
stuff. Simple enough; same approach could be used for other vendors if 
desired.

    <!-- Set a property if we know this is a Sun VM. Can be
         used to enable/disable things based on VM vendor -->
    <condition property="sun-vm" value="true">
    	  <and>
          <equals arg1="Sun Microsystems Inc." arg2="${java.vendor}" 
trim="true"/>
    	  	 <not>
    	  	 	<!-- Pass -Dignore.sun-vm.override=true to ant to bypass
    	  	 	     enabling/disabling things based on Sun being VM vendor -->
    	  	 	<isset property="ignore.sun-vm.override"/>
    	  	 </not>
    	  </and>
    </condition>

Note the JIRA to sort the failure still exists:

https://jira.jboss.org/jira/browse/JBAS-5959

>> If anyone wants to have a go at improving the consistency of the runs, 
>> that would be great.
>>
>> ---
>> http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-TestSuite-jrockit16-jrockit16/99/testReport/ 
>>
>>
>> org.jboss.test.jbossmessaging.test.UnackedUnitTestCase(tests-jbossmessaging).testUnackedTopic    
>>
>> org.jboss.test.jbossmessaging.clustertest.ClusteredTestCase(tests-jbossmessaging-cluster).testSimpleFailover 
>>
>> org.jboss.test.refs.test.ResourceResolutionUnitTestCase.testClientORBResources 
>>
>> org.jboss.test.jca.test.BaseConnectionManagerUnitTestCase.testAllocationRetryMultiThread 
>>
>>
>> ---
>> http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-TestSuite-sun15/1122/testReport/ 
>>
>> org.jboss.test.cluster.classloader.leak.test.FieldGranularityClassloaderLeakUnitTestCase(ClusteredClassLoaderLeak).testFieldWar 
>>
>> org.jboss.test.refs.test.ResourceResolutionUnitTestCase.testClientORBResources 
>>
>>
>> ---
>> http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-TestSuite-sun15-sun16/356/testReport/ 
>>
>>
>> org.jboss.test.cluster.classloader.leak.test.ClassloaderLeakUnitTestCase.testServerFound    
>>
>> org.jboss.test.cluster.classloader.leak.test.FieldGranularityClassloaderLeakUnitTestCase.testFieldWar 
>>
>> org.jboss.test.jbossmessaging.clustertest.ClusteredTestCase(tests-jbossmessaging-cluster).testSimpleFailover 
>>
>> org.jboss.test.jca.test.TxConnectionManagerStressTestCase(tests-standard-stress).testBlockingNoFillTrackByTx 
>>
>> org.jboss.test.timer.test.SecureTimerUnitTestCase(tests-security-basic-unit).testSecuredStatelessSessionBeanTimer 
>>
>> org.jboss.test.refs.test.ResourceResolutionUnitTestCase.testClientORBResources 
>>
>>
>> ---
>> http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-TestSuite-sun16-sun16/263/ 
>>
>>
>> org.jboss.test.classloader.leak.test.AopPreparedClassesClassloaderLeakUnitTestCase.testNoCacheNoReplicableWar 
>>
>> org.jboss.test.classloader.leak.test.AopPreparedClassesClassloaderLeakUnitTestCase.testNoCacheReplicableWar 
>>
>> org.jboss.test.cluster.classloader.leak.test.FieldGranularityClassloaderLeakUnitTestCase(ClusteredClassLoaderLeak).testSimpleReplicableWar 
>>
>> org.jboss.test.cluster.classloader.leak.test.FieldGranularityClassloaderLeakUnitTestCase(ClusteredClassLoaderLeak).testFieldWar 
>>
>> org.jboss.test.jbossmessaging.test.UnackedUnitTestCase(tests-jbossmessaging).testUnackedTopic 
>>
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-development
> 
> 


-- 
Brian Stansberry
Lead, AS Clustering
JBoss, a division of Red Hat
brian.stansberry at redhat.com