[jboss-dev] Re: remaining JBoss-AS-5.1.x-testSuite-sun15 failures

Dimitris Andreadis dandread at redhat.com
Wed Apr 29 04:51:55 EDT 2009


One persisting profileservice test failures seems to be:
org.jboss.test.profileservice.test.ServerManagedObjectsTestCase(profileservice).testWebHost

http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.1.x-testSuite-sun15/lastBuild/testReport/org.jboss.test.profileservice.test/ServerManagedObjectsTestCase(profileservice)/testWebHost/

Scott Stark wrote:
> I see the following test failures in the
> 
>    [junit] Running 
> org.jboss.test.profileservice.test.ServerManagedObjectsTestCase
>    [junit] Tests run: 7, Failures: 3, Errors: 0, Time elapsed: 3.592 sec
>    [junit] Test 
> org.jboss.test.profileservice.test.ServerManagedObjectsTestCase FAILED
>    [junit] Running 
> org.jboss.test.profileservice.test.ServiceBindingManagedObjectsTestCase
>    [junit] Tests run: 7, Failures: 6, Errors: 0, Time elapsed: 1.347 sec
>    [junit] Test 
> org.jboss.test.profileservice.test.ServiceBindingManagedObjectsTestCase 
> FAILED
> 
> The ServerManagedObjectsTestCase failures are 3 web server related errors:
> 
>  <testcase 
> classname="org.jboss.test.profileservice.test.ServerManagedObjectsTestCase" 
> name="testWebConnector" time="0.092">
>    <failure 
> message="jboss.web:name=http-127.0.0.1-8080,type=GlobalRequestProcessor" 
> type="junit.framework.AssertionFailedError">junit.framework.AssertionFailedError: 
> jboss.web:name=http-127.0.0.1-8080,type=GlobalRequestProcessor
>        at 
> org.jboss.test.profileservice.test.ServerManagedObjectsTestCase.testWebConnector(ServerManagedObjectsTestCase.java:269) 
> 
> </failure>
>  </testcase>
>  <testcase 
> classname="org.jboss.test.profileservice.test.ServerManagedObjectsTestCase" 
> name="testWebConnectorPool" time="0.043">
>    <failure message="jboss.web:name=http-127.0.0.1-8080,type=ThreadPool" 
> type="junit.framework.AssertionFailedError">junit.framework.AssertionFailedError: 
> jboss.web:name=http-127.0.0.1-8080,type=ThreadPool
>        at 
> org.jboss.test.profileservice.test.ServerManagedObjectsTestCase.testWebConnectorPool(ServerManagedObjectsTestCase.java:303) 
> 
> </failure>
>  </testcase>
>  <testcase 
> classname="org.jboss.test.profileservice.test.ServerManagedObjectsTestCase" 
> name="testWebHost" time="0.044">
>    <failure message="jboss.web:host=localhost,type=Host" 
> type="junit.framework.AssertionFailedError">junit.framework.AssertionFailedError: 
> jboss.web:host=localhost,type=Host
>        at 
> org.jboss.test.profileservice.test.ServerManagedObjectsTestCase.testWebHost(ServerManagedObjectsTestCase.java:327) 
> 
> </failure>
> 
> Charles Crouch wrote:
>> So what does this mean for r87882 which is going to be the CR?
>>
>> ----- "Scott Stark" <sstark at redhat.com> wrote:
>>
>>  
>>> As of r87884 the ServiceBindingManagedObjectsTestCase are consistent 
>>> with the r87843.
>>>
>>> Dimitris Andreadis wrote:
>>>     
>>> http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.1.x-testSuite-sun15/246/ 
>>>
>>>
>>>    
>>>> r87843
>>>>
>>>> Scott Stark wrote:
>>>>      
>>>>> After getting a clean workspace I'm seeing all but one 
>>>>> ServiceBindingManagedObjectsTestCase fail, so I need to see why
>>>>>         
>>> that    
>>>>> is. What revision was this result based on?
>>>>>         
>>> _______________________________________________
>>> jboss-development mailing list
>>> jboss-development at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>>     
> 



More information about the jboss-development mailing list