Bug 985003 - PartialObjectActivationJarTestCase fails if ran after any of InflowFlatTestCase or TwoModulesOfDifferentTypeTestCase
Summary: PartialObjectActivationJarTestCase fails if ran after any of InflowFlatTestCa...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Testsuite
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ER5
: EAP 6.1.1
Assignee: Ivo Studensky
QA Contact:
URL:
Whiteboard:
: 982637 991486 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-16 14:36 UTC by Ivo Studensky
Modified: 2013-09-16 20:28 UTC (History)
4 users (show)

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

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-1560 0 Major Resolved PartialObjectActivationJarTestCase fails if ran after any of InflowFlatTestCase or TwoModulesOfDifferentTypeTestCase 2013-11-20 08:14:47 UTC

Description Ivo Studensky 2013-07-16 14:36:14 UTC 
Description of problem:

PartialObjectActivationJarTestCase fails if it runs after InflowFlatTestCase as it re-defines a test module structure at runtime which is not supported. Thus, the tests need to use unique module names/slots.


See the upstream JIRA for more details:

https://issues.jboss.org/browse/WFLY-1560
Comment 1 Carlo de Wolf 2013-08-05 07:52:00 UTC 
*** Bug 991486 has been marked as a duplicate of this bug. ***
Comment 2 Pavel Jelinek 2013-08-23 12:27:08 UTC 
Reproducer: https://github.com/istudens/jboss-eap/commit/f99a72cfcd927e6a9f9f62a8cf7095d749240301 
PR: https://github.com/jbossas/jboss-eap/pull/276
This use case was fixed.
Comment 3 Ivo Studensky 2013-08-26 10:34:34 UTC 
*** Bug 991486 has been marked as a duplicate of this bug. ***
Comment 4 Ivo Studensky 2013-08-30 12:20:33 UTC 
*** Bug 982637 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.