[jboss-jira] [JBoss JIRA] (WFCORE-847) Logging unit test fail to use byteman on hp-ux

[Marek Kopecký (JIRA)]

     [ https://issues.jboss.org/browse/WFCORE-847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marek Kopecký closed WFCORE-847.
--------------------------------
    Resolution: Duplicate Issue


Duplicate with https://issues.jboss.org/browse/WFCORE-843

> Logging unit test fail to use byteman on hp-ux
> ----------------------------------------------
>
>                 Key: WFCORE-847
>                 URL: https://issues.jboss.org/browse/WFCORE-847
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Logging, Test Suite
>    Affects Versions: 2.0.0.Alpha11
>         Environment: HP-UX eph-03 B.11.31 U ia64 4052756529
> java version "1.8.0.01-hp-ux"
> Java(TM) SE Runtime Environment (build 1.8.0.01-hp-ux-rc2)
> Java HotSpot(TM) 64-Bit Server VM (build 25.31-b07, mixed mode)
>            Reporter: Marek Kopecký
>            Assignee: James Perkins
>
> *Description of problem:*
> org.jboss.as.logging.LoggingSubsystemRollbackTestCase from wildfly-core fails to load byteman agent on HP-UX.
> *How reproducible:*
> Always
> *Actual results:*
> {noformat}
> Tests run: 7, Failures: 0, Errors: 1, Skipped: 3, Time elapsed: 1.622 sec <<< FAILURE! - in org.jboss.as.logging.LoggingSubsystemRollbackTestCase
> org.jboss.as.logging.LoggingSubsystemRollbackTestCase(org.jboss.as.logging.LoggingSubsystemRollbackTestCase)  Time elapsed: 0.098 sec  <<< ERROR!
> java.lang.Exception: BMUnit : Unable to identify test JVM process during agent load
> 	at org.jboss.byteman.contrib.bmunit.BMUnitConfigState.loadAgent(BMUnitConfigState.java:500)
> 	at org.jboss.byteman.contrib.bmunit.BMUnitConfigState.pushConfigurationState(BMUnitConfigState.java:669)
> 	at org.jboss.byteman.contrib.bmunit.BMUnitRunner$1.evaluate(BMUnitRunner.java:73)
> 	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> 	at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> 	at org.junit.runners.Suite.runChild(Suite.java:127)
> 	at org.junit.runners.Suite.runChild(Suite.java:26)
> 	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> 	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> 	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> 	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> 	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> 	at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> 	at org.junit.runner.JUnitCore.run(JUnitCore.java:160)
> 	at org.junit.runner.JUnitCore.run(JUnitCore.java:138)
> 	at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:113)
> 	at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:85)
> 	at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:54)
> 	at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:134)
> 	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
> 	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
> 	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
> {noformat}
> *Expected results:*
> No errors on output



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)