Bug 967794 - Trace of test suite intermittent failures due to test ordering
Summary: Trace of test suite intermittent failures due to test ordering
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Testsuite
Version: 6.1.0
Hardware: All
OS: Linux
high
low
Target Milestone: ER3
: EAP 6.1.1
Assignee: Chao Wang
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-28 10:58 UTC by Chao Wang
Modified: 2013-09-16 20:29 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-16 20:29:00 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-512 0 Major Resolved Update build to target JDK 7 2015-12-15 16:58:17 UTC

Description Chao Wang 2013-05-28 10:58:46 UTC
Description of problem:

In upstream AS7-6570 aka WFLY-512 (fixes for buiding on JDK7), some test suite intermittent failures failed due to test ordering with different JDK, need to track this for next EAP 6 (6.1.1), here is the list:

testsuite/domain/src/test/java/org/jboss/as/test/integration/domain/management/cli/RolloutPlanTestCase.java
testsuite/integration/basic/src/test/java/org/jboss/as/test/integration/ejb/interceptor/method/EjbMethodInterceptorTestCase.java
testsuite/integration/basic/src/test/java/org/jboss/as/test/integration/ejb/entity/bmp/BMPEntityBeanTestCase.java
testsuite/integration/basic/src/test/java/org/jboss/as/test/integration/jaxrs/jsapi/JaxrsJSApiTestCase.java
testsuite/integration/basic/src/test/java/org/jboss/as/test/integration/jpa/datasourcedefinition/DataSourceDefinitionJPATestCase.java
testsuite/integration/basic/src/test/java/org/jboss/as/test/integration/jpa/epcpropagation/requiresnew/EPCPropagationNewTransactionTestCase.java
testsuite/integration/basic/src/test/java/org/jboss/as/test/integration/jpa/hibernate/envers/implementvalidityauditstrategytest/ImplementValidityAuditStrategyTestCase.java
testsuite/integration/basic/src/test/java/org/jboss/as/test/integration/jpa/secondlevelcache/JPA2LCTestCase.java
testsuite/integration/basic/src/test/java/org/jboss/as/test/integration/jpa/transaction/TransactionTestCase.java
testsuite/integration/basic/src/test/java/org/jboss/as/test/integration/management/api/expression/ExpressionSubstitutionInContainerTestCase.java
testsuite/integration/clust/src/test/java/org/jboss/as/test/clustering/extended/ejb2/stateful/remote/failover/RemoteEJBClientStatefulBeanFailoverTestCase.java



Version-Release number of selected component (if applicable):

next EAP 6, 6.1.1

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:

tests will fail if they execute in different order.

Expected results:

fix the test orders or isolate any connection between tests.

Additional info:

Comment 1 Ivo Studensky 2013-05-31 13:13:22 UTC
Created a PR for this:

https://github.com/jbossas/jboss-eap/pull/158

Comment 2 Rostislav Svoboda 2013-06-07 09:58:33 UTC
QA_ACK granted, AS TS fix.

Comment 3 Pavel Jelinek 2013-08-02 13:55:53 UTC
Fixed in 6.1.1.ER3


Note You need to log in before you can comment on or make changes to this bug.