[jboss-as7-dev] consistent testsuite failures since I synced with master yesterday

[Scott Marlow]

How did these testsuite failures slip in?  From my own experience 
running the updated testsuite, it looks like we now have an allTests 
profile that doesn't run the integration tests.  Perhaps we merged some 
changes and only ran the allTests profile.  I think that we need to 
continue to use -DallTests instead (that includes the integration 
tests).  Does anyone know more?

I'm not sure why some people aren't seeing the failures but it seems we 
need to track backwards from the symptoms (listed below) or rollback 
some changes until it goes away.

If anyone is working on tracking the cause down, please speak up.  I can 
jump in but don't want to duplicate effort.

Scott

On 10/18/2011 02:15 PM, Scott Marlow wrote:
> The hudson AS7 test just finished with all integration tests passing.
>
> When you say that your using a fresh master, is that a new AS7 source
> tree or an existing one freshly synced with AS7 master?
>
>
> On 10/18/2011 12:26 PM, Scott Marlow wrote:
>> On 10/18/2011 08:57 AM, Ondřej Žižka wrote:
>>> I have a fresh master and testsuite runs fine.
>>> Except 2 failures (for which I also seek comments):
>>>
>>> org.jboss.as.test.integration.osgi.webapp.ServletIntegrationTestCase.testServiceAccess
>>> org.jboss.as.test.integration.osgi.jaxrs.RestEasyIntegrationTestCase.org.jboss.as.test.integration.osgi.jaxrs.RestEasyIntegrationTestCase
>>>
>>> server.log:
>>> http://pastebin.test.redhat.com/64949
>>
>> I didn't see that failure.
>>
>> Which folder are you starting the unit test from and what is your
>> command line?
>>
>> I was trying to use "mvn clean install -DallTests" in the
>> as7/testsuite/integration folder.
>>
>> When I checked earlier, Hudson wasn't running the full test (was using
>> -PallTests instead of -DallTests).  Looks like someone changed that but
>> the test is still in queue.
>>
>>
>>>
>>> Anyone seeing that? I thought it could be a race condition caused by
>>> improper use of deployer API, but giving it some time after deploy
>>> didn't help.
>>>
>>> Ondra
>>>
>>>
>>>
>>> Scott Marlow píše v Út 18. 10. 2011 v 08:36 -0400:
>>>
>>>> When running the as7/testsuite/integration tests, we run fine for a
>>>> while but then "OutOfMemoryError: unable to create new native thread"
>>>> errors start showing up in the server.log.
>>>>
>>>> Failing tests are here http://pastebin.com/D3SeJ2rP
>>>>
>>>> AS7 thread dump showing a lot of "JMX server connection timeout NNN"
>>>> threads is here http://pastebin.com/qDC52WJG
>>>>
>>>> To recreate change into as7/testsuite/integration and do a "mvn clean
>>>> install -DallTests".
>>>>
>>>> Is anyone not seeing this after syncing with master?
>>>>
>>>> Scott
>>>> _______________________________________________
>>>> jboss-as7-dev mailing list
>>>> jboss-as7-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>
>>
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev