[JBoss JIRA] (JBTM-1767) restat-api failures with emma: Tests run: 30, Failures: 11, Errors: 2
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-1767?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-1767:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> restat-api failures with emma: Tests run: 30, Failures: 11, Errors: 2
> ---------------------------------------------------------------------
>
> Key: JBTM-1767
> URL: https://issues.jboss.org/browse/JBTM-1767
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: REST, Testing
> Reporter: Tom Jenkinson
> Assignee: Michael Musgrove
> Priority: Minor
> Fix For: 5.0.0.M4
>
>
> Failed tests: test1PCAbort(org.jboss.jbossts.star.test.CoordinatorTest): expected:<v[2]> but was:<v[1]>
> test2PC(org.jboss.jbossts.star.test.CoordinatorTest): expected:<v[2]> but was:<v[1]>
> testEnlistVolatileParticipant(org.jboss.jbossts.star.test.OptionalSpecTest): null expected:<[0]> but was:<[4]>
> testRecoveryURLTwoPhaseAwareWithoutNotification(org.jboss.jbossts.star.test.SpecTest): null expected:<Transaction[RolledBack]> but was:<Transaction[Active]>
> testRecoveryURLTwoPhaseAwareWithNotification(org.jboss.jbossts.star.test.SpecTest): null expected:<Transaction[Committed]> but was:<Transaction[Active]>
> testRecoveryURLTwoPhaseUnawareWithoutNotification(org.jboss.jbossts.star.test.SpecTest): null expected:<Transaction[RolledBack]> but was:<Transaction[Active]>
> testRecoveryURLTwoPhaseUnawareWithNotification(org.jboss.jbossts.star.test.SpecTest): null expected:<Transaction[Committed]> but was:<Transaction[Active]>
> testHeuristic(org.jboss.jbossts.star.test.SpecTest): null expected:<txstatus=Transaction[HeuristicMixed]> but was:<txstatus=Transaction[RolledBack]>
> testHeuristicWithForget(org.jboss.jbossts.star.test.SpecTest): null expected:<txstatus=Transaction[HeuristicRollb]ack> but was:<txstatus=Transaction[RolledB]ack>
> testSpec6(org.jboss.jbossts.star.test.SpecTest): null expected:<txstatus=Transaction[RolledBack]> but was:<txstatus=Transaction[Committed]>
> testCannotEnlistDuring2PC(org.jboss.jbossts.star.test.SpecTest): expected:<500> but was:<412>
> Tests in error:
> testTransactionStatistics(org.jboss.jbossts.star.test.OptionalSpecTest): org.jboss.jbossts.star.util.media.txstatusext.TransactionManagerElement cannot be cast to org.jboss.jbossts.star.util.media.txstatusext.TransactionStatisticsElement
> testParticipantStatus(org.jboss.jbossts.star.test.SpecTest): Unexpected status. Expected 200 got 404
--
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
11 years, 5 months
[JBoss JIRA] (JBTM-1767) restat-api failures with emma: Tests run: 30, Failures: 11, Errors: 2
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-1767?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-1767:
-----------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/jbosstm/narayana/pull/338
> restat-api failures with emma: Tests run: 30, Failures: 11, Errors: 2
> ---------------------------------------------------------------------
>
> Key: JBTM-1767
> URL: https://issues.jboss.org/browse/JBTM-1767
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: REST, Testing
> Reporter: Tom Jenkinson
> Assignee: Michael Musgrove
> Priority: Minor
> Fix For: 5.0.0.M4
>
>
> Failed tests: test1PCAbort(org.jboss.jbossts.star.test.CoordinatorTest): expected:<v[2]> but was:<v[1]>
> test2PC(org.jboss.jbossts.star.test.CoordinatorTest): expected:<v[2]> but was:<v[1]>
> testEnlistVolatileParticipant(org.jboss.jbossts.star.test.OptionalSpecTest): null expected:<[0]> but was:<[4]>
> testRecoveryURLTwoPhaseAwareWithoutNotification(org.jboss.jbossts.star.test.SpecTest): null expected:<Transaction[RolledBack]> but was:<Transaction[Active]>
> testRecoveryURLTwoPhaseAwareWithNotification(org.jboss.jbossts.star.test.SpecTest): null expected:<Transaction[Committed]> but was:<Transaction[Active]>
> testRecoveryURLTwoPhaseUnawareWithoutNotification(org.jboss.jbossts.star.test.SpecTest): null expected:<Transaction[RolledBack]> but was:<Transaction[Active]>
> testRecoveryURLTwoPhaseUnawareWithNotification(org.jboss.jbossts.star.test.SpecTest): null expected:<Transaction[Committed]> but was:<Transaction[Active]>
> testHeuristic(org.jboss.jbossts.star.test.SpecTest): null expected:<txstatus=Transaction[HeuristicMixed]> but was:<txstatus=Transaction[RolledBack]>
> testHeuristicWithForget(org.jboss.jbossts.star.test.SpecTest): null expected:<txstatus=Transaction[HeuristicRollb]ack> but was:<txstatus=Transaction[RolledB]ack>
> testSpec6(org.jboss.jbossts.star.test.SpecTest): null expected:<txstatus=Transaction[RolledBack]> but was:<txstatus=Transaction[Committed]>
> testCannotEnlistDuring2PC(org.jboss.jbossts.star.test.SpecTest): expected:<500> but was:<412>
> Tests in error:
> testTransactionStatistics(org.jboss.jbossts.star.test.OptionalSpecTest): org.jboss.jbossts.star.util.media.txstatusext.TransactionManagerElement cannot be cast to org.jboss.jbossts.star.util.media.txstatusext.TransactionStatisticsElement
> testParticipantStatus(org.jboss.jbossts.star.test.SpecTest): Unexpected status. Expected 200 got 404
--
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
11 years, 5 months
[JBoss JIRA] (JBTM-1778) JBossTS qa testsuite fails on HP-UX
by Ondřej Chaloupka (JIRA)
Ondřej Chaloupka created JBTM-1778:
--------------------------------------
Summary: JBossTS qa testsuite fails on HP-UX
Key: JBTM-1778
URL: https://issues.jboss.org/browse/JBTM-1778
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.6.1.CP13
Reporter: Ondřej Chaloupka
Assignee: Michael Musgrove
Hi Michael,
as part of the EAP5.2.0 certification tests running on HP-UX 11v3 machines.
I've hit problems with several testcases in the ts testsuite.
We are testing on machines under this tag: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/label/hpux11v3/
As I think that you know the testsuite the most I'm assigning this issue to you. If I've mistaken, please, reassign it.
Those are:
- jbossts-qa-currenttests01 number 20 stays stuck forever. It stays on current.resume call. I'm adding the jstack output, that I've got from the call, as attachment here.
- jbossts-qa-jtatests01 number 005 fails with error message:
java.lang.Exception: Test failed! JTATests01_Test005 got 1 fewer task passes than expected
- jbossts-qa-otsserver number 010, 011, 012 and 017 fail with the error
got 1 fewer task passes than expected
I've tried to get some closer knowledge about the problem but I wasn't able much.
Others tests from testsuite pass fine without error. Just their run time is longer in comparison with testsuite running on RHEL.
We are running tests on jdk6 and jdk7 on 32bits and 64bits. These particular results belong to jdk6 and 32b.
The jenkins run could be found at:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap5-jbossts-testsui...
Would you have some suggestion about this?
--
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
11 years, 5 months
[JBoss JIRA] (JBTM-1772) Cannot build with emma as dependency on adinn.jar?
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-1772?page=com.atlassian.jira.plugin.... ]
Michael Musgrove edited comment on JBTM-1772 at 6/11/13 9:56 AM:
-----------------------------------------------------------------
The workaround is:
mvn install:install-file -Dfile=<BUILD_DIR>/ext/emma.jar -DgroupId=emma -DartifactId=emma -Dversion=2.0.12224-adinn -Dpackaging=jar
was (Author: mmusgrov):
The workaround is:
mvn install:install-file -Dfile=/home/mmusgrov/source/forks/narayana/narayana/ext/emma.jar -DgroupId=emma -DartifactId=emma -Dversion=2.0.12224-adinn -Dpackaging=jar
> Cannot build with emma as dependency on adinn.jar?
> --------------------------------------------------
>
> Key: JBTM-1772
> URL: https://issues.jboss.org/browse/JBTM-1772
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Build System, Testing
> Affects Versions: 5.0.0.M4
> Environment: Mac OS 10.7
> Reporter: Mark Little
> Assignee: Tom Jenkinson
> Priority: Blocker
>
> When trying to build STM with emma as per 1766 instructions, I get the following build time error:
> /Users/marklittle/github/narayana/tools/maven/bin/mvn -s tools/maven/conf/settings.xml -Dorson.jar.location=/Users/marklittle/github/narayana/ext/ -Demma.jar.location=/Users/marklittle/github/narayana/ext/emma.jar clean install -PcodeCoverage -pl STM
> [INFO] Scanning for projects...
> [INFO]
> [INFO] ------------------------------------------------------------------------
> [INFO] Building Narayana: STM 5.0.0.M4-SNAPSHOT
> [INFO] ------------------------------------------------------------------------
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ core ---
> [INFO]
> [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ core ---
> [debug] execute contextualize
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory /Users/marklittle/github/narayana/STM/src/main/resources
> [INFO]
> [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ core ---
> [INFO] Compiling 40 source files to /Users/marklittle/github/narayana/STM/target/classes
> [INFO]
> [INFO] --- emma-maven-plugin:1.0-alpha-3:instrument (default) @ core ---
> Downloading: http://repository.jboss.org/nexus/content/groups/public/emma/emma/2.0.122...
> Downloading: http://repo.maven.apache.org/maven2/emma/emma/2.0.12224-adinn/emma-2.0.12...
> [WARNING] The POM for emma:emma:jar:2.0.12224-adinn is missing, no dependency information available
> Downloading: http://repository.jboss.org/nexus/content/groups/public/emma/emma/2.0.122...
> Downloading: http://repo.maven.apache.org/maven2/emma/emma/2.0.12224-adinn/emma-2.0.12...
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 4.095s
> [INFO] Finished at: Sun Jun 09 15:31:51 BST 2013
> [INFO] Final Memory: 23M/207M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.codehaus.mojo:emma-maven-plugin:1.0-alpha-3:instrument (default) on project core: Execution default of goal org.codehaus.mojo:emma-maven-plugin:1.0-alpha-3:instrument failed: Plugin org.codehaus.mojo:emma-maven-plugin:1.0-alpha-3 or one of its dependencies could not be resolved: Could not find artifact emma:emma:jar:2.0.12224-adinn in jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public/) -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
--
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
11 years, 5 months
[JBoss JIRA] (JBTM-1554) Create a job for PR on 5_BRANCH and 4_BRANCH
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1554?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1554:
--------------------------------
Fix Version/s: (was: 4.17.5)
> Create a job for PR on 5_BRANCH and 4_BRANCH
> --------------------------------------------
>
> Key: JBTM-1554
> URL: https://issues.jboss.org/browse/JBTM-1554
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Build System
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M4
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> This will allow us to test changes to our AS fork before merging. I suggest we run all the tests that AS run on lightning, followed by all the Narayana tests.
> We should also come up with a plan for building PR on 4_BRANCH or 5_BRANCH and Narayana together. This is required for situations when we need to make commits to both code basis that are mutually dependent.
--
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
11 years, 5 months
[JBoss JIRA] (JBTM-1554) Create a job for PR on 5_BRANCH
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1554?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1554:
--------------------------------
Summary: Create a job for PR on 5_BRANCH (was: Create a job for PR on 5_BRANCH and 4_BRANCH)
> Create a job for PR on 5_BRANCH
> -------------------------------
>
> Key: JBTM-1554
> URL: https://issues.jboss.org/browse/JBTM-1554
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Build System
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M4
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> This will allow us to test changes to our AS fork before merging. I suggest we run all the tests that AS run on lightning, followed by all the Narayana tests.
> We should also come up with a plan for building PR on 4_BRANCH or 5_BRANCH and Narayana together. This is required for situations when we need to make commits to both code basis that are mutually dependent.
--
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
11 years, 5 months
[JBoss JIRA] (JBTM-1777) Set up a CI job to run codeCoverage tests
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1777?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on JBTM-1777:
-------------------------------------
Job here: http://172.17.131.2/view/Narayana+BlackTie/job/narayana-codeCoverage
Being tested now...
> Set up a CI job to run codeCoverage tests
> -----------------------------------------
>
> Key: JBTM-1777
> URL: https://issues.jboss.org/browse/JBTM-1777
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Testing
> Reporter: Tom Jenkinson
> Assignee: Tom Jenkinson
> Fix For: 5.0.0.M4
>
>
> We do not currently run automated code coverage report generation in CI. It would be worth setting up a job to run this weekly. I imagine all the tests will need to be run on the same node unless we get aggregation to work and that is why I am thinking it will be a new job rather than a modification of the existing job (which runs different parts of the build in parallel on different nodes).
> If we were to get aggregation to work it may be possible (if it doesn't add much time to the build) to run this profile in CI.
> We should also determine suitable coverage metrics to aim for.
--
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
11 years, 5 months
[JBoss JIRA] (JBTM-1777) Set up a CI job to run codeCoverage tests
by Tom Jenkinson (JIRA)
Tom Jenkinson created JBTM-1777:
-----------------------------------
Summary: Set up a CI job to run codeCoverage tests
Key: JBTM-1777
URL: https://issues.jboss.org/browse/JBTM-1777
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Testing
Reporter: Tom Jenkinson
Assignee: Tom Jenkinson
Fix For: 5.0.0.M4
We do not currently run automated code coverage report generation in CI. It would be worth setting up a job to run this weekly. I imagine all the tests will need to be run on the same node unless we get aggregation to work and that is why I am thinking it will be a new job rather than a modification of the existing job (which runs different parts of the build in parallel on different nodes).
If we were to get aggregation to work it may be possible (if it doesn't add much time to the build) to run this profile in CI.
We should also determine suitable coverage metrics to aim for.
--
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
11 years, 5 months
[JBoss JIRA] (JBTM-1764) REST-AT coordinator does not handle commit correctly for transactions marked rollback only
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-1764?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-1764:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
When committing a transaction the spec says
{quote}
325The state of the transaction MUST be TransactionActive for this operation to succeed
{quote}
Although it is not explicitly stated what should happen if the state is TransactionRollbackOnly, I think it is reasonably clear the intent is to rollback such a transaction in this state and therefore the fix allows the transaction to proceed to rollback when asked to commit in this state. We'll update the spec to clarify the intent.
Note that there is a similar check which refuses participant enlistment in a transaction that is marked rollback only. This is in compliance with the spec:
{quote}
385If the transaction is not TransactionActive when registration is attempted, then the implementation
386MUST return a 412 status code.
{quote}
and is reasonable so I still refuse the enlistment when the transaction is in this state. Note that a "participant" can still take part in Volatile phase of the protocol (cf Synchronizations) to discover the outcome of a transaction even if it has been marked rollback only.
> REST-AT coordinator does not handle commit correctly for transactions marked rollback only
> ------------------------------------------------------------------------------------------
>
> Key: JBTM-1764
> URL: https://issues.jboss.org/browse/JBTM-1764
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: REST
> Affects Versions: 5.0.0.M3
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Fix For: 5.0.0.M4
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> The REST-AT coordinator does not automatically roll back a transaction marked TransactionRollbackOnly if asked to commit.
--
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
11 years, 5 months