[jboss-as7-dev] Testsuite fails early, hence has insufficient regression detection

Darran Lofthouse darran.lofthouse at jboss.com
Fri Nov 25 06:02:11 EST 2011


+1 With some of the testsuite instability I experienced in the last 
couple of weeks a single flag to force a full run with a summary at the 
very end would have helped a lot.

On 11/25/2011 10:52 AM, Thomas Diesler wrote:
> Folks,
>
> when running
>
> ./integration-tests.sh -Dbasic-tests clean install
>
> I see failures like this
>
>     Results :
>
>     Failed tests:
>     testChangeMessagePriority(org.jboss.as.test.integration.messaging.mgmt.CoreQueueManagementTestCase):
>     expected:<3> but was:<1>
>
>     Tests in error:
>     testAddJndi(org.jboss.as.test.integration.messaging.mgmt.JMSQueueManagementTestCase):
>     java.io.IOException: JBAS010625: Channel closed
>
>     Tests run: 210, Failures: 1, Errors: 1, Skipped: 5
>
> After that the testrun stops and the larger portion of the test suite is
> not executed. A cannot see if I have regression in jax, osgi, etc
> If the basic tests must always succeed (i.e. like the smoke tests) they
> should be smoke tests to start of with.
>
> Perhaps there is some magic to run the full set of basic integration
> tests, is there?
>
> cheers
> -thomas
>
> PS: -fae does not make a difference
>
> --
> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Thomas Diesler
> JBoss OSGi Lead
> JBoss, a division of Red Hat
> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
>
>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev


More information about the jboss-as7-dev mailing list