[JBoss JIRA] (JBTM-1082) Emma not working on JDK7
by Ondřej Chaloupka (JIRA)
[ https://issues.jboss.org/browse/JBTM-1082?page=com.atlassian.jira.plugin.... ]
Ondřej Chaloupka resolved JBTM-1082.
------------------------------------
Resolution: Done
In case of necessity of running emma on jdk7, please, use workaround of activating old verifier.
> Emma not working on JDK7
> ------------------------
>
> Key: JBTM-1082
> URL: https://issues.jboss.org/browse/JBTM-1082
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Build System, Testing
> Reporter: Tom Jenkinson
> Assignee: Ondřej Chaloupka
>
> -Demma.enabled=true does not work on JDK7
> Testcase: testNullInput took 0.006 sec
> Caused an ERROR
> Expecting a stackmap frame at branch target 11 in method com.arjuna.common.util.propertyservice.StringPropertyReplacer.<init>()V at offset 4
> java.lang.VerifyError: Expecting a stackmap frame at branch target 11 in method com.arjuna.common.util.propertyservice.StringPropertyReplacer.<init>()V at offset 4
> at com.arjuna.common.tests.propertyservice.StringPropertyReplacerUnitTestCase.testNullInput(StringPropertyReplacerUnitTestCase.java:86)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (JBTM-1082) Emma not working on JDK7
by Ondřej Chaloupka (JIRA)
[ https://issues.jboss.org/browse/JBTM-1082?page=com.atlassian.jira.plugin.... ]
Ondřej Chaloupka commented on JBTM-1082:
----------------------------------------
Jonathan: OK, I see, thanks.
As what Jonathan pointed out the workaround is from my point of view sufficient for closing this jira.
It's already planned to move to jacoco for new versions of narayana.
> Emma not working on JDK7
> ------------------------
>
> Key: JBTM-1082
> URL: https://issues.jboss.org/browse/JBTM-1082
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Build System, Testing
> Reporter: Tom Jenkinson
> Assignee: Ondřej Chaloupka
>
> -Demma.enabled=true does not work on JDK7
> Testcase: testNullInput took 0.006 sec
> Caused an ERROR
> Expecting a stackmap frame at branch target 11 in method com.arjuna.common.util.propertyservice.StringPropertyReplacer.<init>()V at offset 4
> java.lang.VerifyError: Expecting a stackmap frame at branch target 11 in method com.arjuna.common.util.propertyservice.StringPropertyReplacer.<init>()V at offset 4
> at com.arjuna.common.tests.propertyservice.StringPropertyReplacerUnitTestCase.testNullInput(StringPropertyReplacerUnitTestCase.java:86)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (JBTM-1082) Emma not working on JDK7
by Jonathan Halliday (JIRA)
[ https://issues.jboss.org/browse/JBTM-1082?page=com.atlassian.jira.plugin.... ]
Jonathan Halliday commented on JBTM-1082:
-----------------------------------------
Come off it, the emma jdk6 binaries are fine. java goes to great lengths to ensure that binaries built with older jdks still run on newer ones. The error trace is not from emma code. It's from code that emma has instrumented. The changes emma is making to the arjuna code don't pass the newer verifier.
http://www.oracle.com/technetwork/java/javase/jdk7-relnotes-418459.html
It's not worth patching emma, which is largely defunct, to emit the more recent bytecode. Move to jacoco instead.
> Emma not working on JDK7
> ------------------------
>
> Key: JBTM-1082
> URL: https://issues.jboss.org/browse/JBTM-1082
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Build System, Testing
> Reporter: Tom Jenkinson
> Assignee: Ondřej Chaloupka
>
> -Demma.enabled=true does not work on JDK7
> Testcase: testNullInput took 0.006 sec
> Caused an ERROR
> Expecting a stackmap frame at branch target 11 in method com.arjuna.common.util.propertyservice.StringPropertyReplacer.<init>()V at offset 4
> java.lang.VerifyError: Expecting a stackmap frame at branch target 11 in method com.arjuna.common.util.propertyservice.StringPropertyReplacer.<init>()V at offset 4
> at com.arjuna.common.tests.propertyservice.StringPropertyReplacerUnitTestCase.testNullInput(StringPropertyReplacerUnitTestCase.java:86)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (JBTM-1082) Emma not working on JDK7
by Ondřej Chaloupka (JIRA)
[ https://issues.jboss.org/browse/JBTM-1082?page=com.atlassian.jira.plugin.... ]
Ondřej Chaloupka commented on JBTM-1082:
----------------------------------------
As workaround is possible to define java opt argument -XX:-UseSplitVerifier
Put it to file sharedbuild.xml to the tag <junit> like:
<jvmarg value="-XX:-UseSplitVerifier" />
I suppose that this problem is caused by the fact that the emma library was compiled with older version of compiler that we are trying to use for compiling TS sources.
Some links e.g. here http://stackoverflow.com/questions/7970622/java-7-jvm-verifyerror-in-eclipse
Do you think that the workaround is enough for solving this jira or should be tried to recompile emma or dive to some other investigation?
> Emma not working on JDK7
> ------------------------
>
> Key: JBTM-1082
> URL: https://issues.jboss.org/browse/JBTM-1082
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Build System, Testing
> Reporter: Tom Jenkinson
> Assignee: Ondřej Chaloupka
>
> -Demma.enabled=true does not work on JDK7
> Testcase: testNullInput took 0.006 sec
> Caused an ERROR
> Expecting a stackmap frame at branch target 11 in method com.arjuna.common.util.propertyservice.StringPropertyReplacer.<init>()V at offset 4
> java.lang.VerifyError: Expecting a stackmap frame at branch target 11 in method com.arjuna.common.util.propertyservice.StringPropertyReplacer.<init>()V at offset 4
> at com.arjuna.common.tests.propertyservice.StringPropertyReplacerUnitTestCase.testNullInput(StringPropertyReplacerUnitTestCase.java:86)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (JBTM-1407) Have a build option that builds JTS only against JacORB or IDLJ, but not both.
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-1407?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris logged work on JBTM-1407:
-----------------------------------------
Author: Gytis Trikleris
Created on: 11/Jan/13 1:16 PM
Start Date: 11/Jan/13 11:20 AM
Worklog Time Spent: 2 hours
Issue Time Tracking
-------------------
Remaining Estimate: 20 minutes (was: 0 minutes)
Time Spent: 2 hours, 40 minutes (was: 40 minutes)
Worklog Id: (was: 12428343)
> Have a build option that builds JTS only against JacORB or IDLJ, but not both.
> ------------------------------------------------------------------------------
>
> Key: JBTM-1407
> URL: https://issues.jboss.org/browse/JBTM-1407
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: JTS
> Affects Versions: 4.17.3
> Reporter: Mark Little
> Assignee: Gytis Trikleris
> Fix For: 5.0.0.M2
>
> Time Spent: 2 hours, 40 minutes
> Remaining Estimate: 20 minutes
>
> This boils down to supporting two new profiles:
> ./build.sh -P jts-jacorb
> ./build.sh -P jts-idlj
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (JBTM-1420) org.apache.commons.io.output.DeferredFileOutputStream class not found
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1420?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1420:
--------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/jbossas/jboss-as/pull/3866
> org.apache.commons.io.output.DeferredFileOutputStream class not found
> ---------------------------------------------------------------------
>
> Key: JBTM-1420
> URL: https://issues.jboss.org/browse/JBTM-1420
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Testing, TXFramework
> Reporter: Gytis Trikleris
> Assignee: Paul Robinson
> Priority: Critical
> Fix For: 5.0.0.M2
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> See: http://172.17.131.2/job/narayana/139
> {noformat}
> Tests in error:
> clientDrivenCommitTest(org.jboss.narayana.txframework.functional.rest.at.simpleEJB.ClientTXInterceptorTest): java.lang.NoClassDefFoundError: org/apache/commons/io/output/DeferredFileOutputStream
> multipleInvokeTest(org.jboss.narayana.txframework.functional.rest.at.simpleEJB.IndirectTXManagementTest): org/apache/commons/io/output/DeferredFileOutputStream
> clientDrivenRollbackTest(org.jboss.narayana.txframework.functional.rest.at.simpleEJB.IndirectTXManagementTest): org/apache/commons/io/output/DeferredFileOutputStream
> participantDrivenRollbackTest(org.jboss.narayana.txframework.functional.rest.at.simpleEJB.IndirectTXManagementTest): org/apache/commons/io/output/DeferredFileOutputStream
> clientDrivenCommitTest(org.jboss.narayana.txframework.functional.rest.at.simpleEJB.IndirectTXManagementTest): org/apache/commons/io/output/DeferredFileOutputStream
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (JBTM-1420) org.apache.commons.io.output.DeferredFileOutputStream class not found
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1420?page=com.atlassian.jira.plugin.... ]
Paul Robinson logged work on JBTM-1420:
---------------------------------------
Author: Paul Robinson
Created on: 11/Jan/13 11:32 AM
Start Date: 11/Jan/13 11:32 AM
Worklog Time Spent: 1 hour, 30 minutes
Issue Time Tracking
-------------------
Remaining Estimate: 6 hours, 30 minutes (was: 1 day)
Time Spent: 1 hour, 30 minutes
Worklog Id: (was: 12428342)
> org.apache.commons.io.output.DeferredFileOutputStream class not found
> ---------------------------------------------------------------------
>
> Key: JBTM-1420
> URL: https://issues.jboss.org/browse/JBTM-1420
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Testing, TXFramework
> Reporter: Gytis Trikleris
> Assignee: Paul Robinson
> Priority: Critical
> Fix For: 5.0.0.M2
>
> Original Estimate: 1 day
> Time Spent: 1 hour, 30 minutes
> Remaining Estimate: 6 hours, 30 minutes
>
> See: http://172.17.131.2/job/narayana/139
> {noformat}
> Tests in error:
> clientDrivenCommitTest(org.jboss.narayana.txframework.functional.rest.at.simpleEJB.ClientTXInterceptorTest): java.lang.NoClassDefFoundError: org/apache/commons/io/output/DeferredFileOutputStream
> multipleInvokeTest(org.jboss.narayana.txframework.functional.rest.at.simpleEJB.IndirectTXManagementTest): org/apache/commons/io/output/DeferredFileOutputStream
> clientDrivenRollbackTest(org.jboss.narayana.txframework.functional.rest.at.simpleEJB.IndirectTXManagementTest): org/apache/commons/io/output/DeferredFileOutputStream
> participantDrivenRollbackTest(org.jboss.narayana.txframework.functional.rest.at.simpleEJB.IndirectTXManagementTest): org/apache/commons/io/output/DeferredFileOutputStream
> clientDrivenCommitTest(org.jboss.narayana.txframework.functional.rest.at.simpleEJB.IndirectTXManagementTest): org/apache/commons/io/output/DeferredFileOutputStream
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (JBTM-1382) QA build does not archive test group summary files
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1382?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on JBTM-1382:
-------------------------------------
Yeah, that builds zip look fine to me, as far as I am concerned this can be marked as resolved - thanks
> QA build does not archive test group summary files
> --------------------------------------------------
>
> Key: JBTM-1382
> URL: https://issues.jboss.org/browse/JBTM-1382
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Testing
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Priority: Minor
> Fix For: 5.0.0.M2
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> The QA test suite consists of a number of test groups. The build produces a summary file showing the status of each sub test within a group (these are called TEST-<test group>.txt and stored in the qa directory). We currently archive the qa/testoutput directory but it would be useful to also archive these summary text files. Note that we cannot rely on Jenkins to do this for us since the jts remote test group is executed twice (once for each orb) and the files from the first run are overwritten.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months