[JBoss JIRA] (JBTM-1770) Fix up pretty-printing of success/failures in build
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1770?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1770:
--------------------------------
Hi Mike,
This issue was marked as "Resolved, Done" but there is no "Fix Version" specified. Please can you update the Jira with the version of the software where you fixed this? Also, can you then close the issue (assuming its not an in development version).
Thanks,
Tom
> Fix up pretty-printing of success/failures in build
> ---------------------------------------------------
>
> Key: JBTM-1770
> URL: https://issues.jboss.org/browse/JBTM-1770
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Build System
> Affects Versions: 5.0.0.M4
> Reporter: Mark Little
> Assignee: Michael Musgrove
> Priority: Trivial
>
> TS jtax .......................... SUCCESS [1:02.017s]
> [INFO] Narayana: ArjuntaJTS narayana-jts-jacorb .......... SUCCESS [7.963s]
> [INFO] Narayana: ArjunaJTS integration ................... SUCCESS [33.609s]
> [INFO] Narayana: rest-tx ................................. SUCCESS [0.009s]
> [INFO] Narayana: rest-tx util ............................ SUCCESS [2.646s]
> [INFO] Narayana: rest-tx tx (RESTful API for Atomic Transactions) SUCCESS [34.522s]
> [INFO] Narayana: rest-tx webservice ...................... SUCCESS [0.720s]
> [INFO] Narayana: rest-tx integration ..................... SUCCESS [4.862s]
> [INFO] Narayana: txbridge ................................ SUCCESS [3.460s]
> [INFO] Narayana: fileio .................................. SUCCESS [1.089s]
> [INFO] Narayana: STM ..................................... SUCCESS [29.172s]
> [INFO] Narayana: txframework ............................. SUCCESS [2.526s]
> [INFO] Narayana: narayana-full ........................... SUCCESS [13.753s]
> Maybe remove the (RESTful API for Atomic Transactions) text, or shorten it.
--
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
10 years, 8 months
[JBoss JIRA] (JBTM-1166) Remove dependency on AS6 component matrix in the REST module
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1166?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1166:
--------------------------------
Hi Mike,
This issue was marked as "Resolved, Done" but there is no "Fix Version" specified. Please can you update the Jira with the version of the software where you fixed this? Also, can you then close the issue (assuming its not an in development version).
Thanks,
Tom
> Remove dependency on AS6 component matrix in the REST module
> ------------------------------------------------------------
>
> Key: JBTM-1166
> URL: https://issues.jboss.org/browse/JBTM-1166
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: REST
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
>
> The REST module still contains a dependency on the AS6 component matrix. Update the pom to use jboss-javaee-6.0 for dependency management.
--
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
10 years, 8 months
[JBoss JIRA] (JBTM-264) Improve tooling
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-264?page=com.atlassian.jira.plugin.s... ]
Tom Jenkinson updated JBTM-264:
-------------------------------
Hi Mike,
This issue was marked as "Resolved, Done" but there is no "Fix Version" specified. Please can you update the Jira with the version of the software where you fixed this? Also, can you then close the issue (assuming its not an in development version).
Thanks,
Tom
> Improve tooling
> ---------------
>
> Key: JBTM-264
> URL: https://issues.jboss.org/browse/JBTM-264
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Tooling
> Affects Versions: 4.2.3.SP5
> Reporter: Mark Little
> Assignee: Michael Musgrove
>
> We need better tools support.
--
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
10 years, 8 months
[JBoss JIRA] (JBTM-1601) Failing qa testcase org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery02_2 on windows machines with jacorb
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1601?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1601:
--------------------------------
Hi Mike,
This issue was marked as "Resolved, Done" but there is no "Fix Version" specified. Please can you update the Jira with the version of the software where you fixed this? Also, can you then close the issue (assuming its not an in development version).
Thanks,
Tom
> Failing qa testcase org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery02_2 on windows machines with jacorb
> --------------------------------------------------------------------------------------------------------------------
>
> Key: JBTM-1601
> URL: https://issues.jboss.org/browse/JBTM-1601
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Testing
> Affects Versions: 4.17.3, 5.0.0.M2
> Reporter: Ondřej Chaloupka
> Assignee: Michael Musgrove
>
> I'm hitting an issue on qa tests for windows machines. I'm currently testing EAP 6.1.0.ER3.
> Testcase org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery02_2 is failing when it's run on windows machines. It does not matter which JDK is used. It fails on 4.17 branch and master as well.
> This happens for jacorb.
> The fails consistently occur on 5 tests from the testcase - that are from CrashRecovery02_2_Test26 till CrashRecovery02_2_Test30.
> All of them throw assertion:
> {quote}
> junit.framework.AssertionFailedError: task client1 printed Failed.
> {quote}
> These details apply to test CrashRecovery02_2_Test27:
> The client implementation is org.jboss.jbossts.qa.CrashRecovery02.Client02a and the fail comes from line 114 (branch 4.17).
> {code}
> correct = correct && (resourceTrace1 == ResourceTrace.ResourceTraceCommit);
> {code}
> Where the value of resourceTrace1 is {{ResourceTraceNone}}.
> I didn't get with investigation further so far.
> Steps for reproducing could be handy (using narayana.sh script first):
> 1. export NARAYANA_BUILD=0
> export NARAYANA_TESTS=0
> export CP_NARAYANA_AS=0
> export AS_BUILD=0
> export XTS_AS_TESTS=0
> export TXF_TESTS=0
> export XTS_TESTS=0
> export txbridge=0
> export QA_TESTS=1
> export SUN_ORB=0
> export QA_TARGET=test
> export QA_PROFILE="-Dtest=crashrecovery02_2"
> export WORKSPACE=$PWD
> 2. run naryana.sh - there was problem with paths for me so the command looks like this at the end
> {quote}
> sh scripts/hudson/narayana.sh -Demma.jar.location=c:\\tmp\\ochaloup\\ext -Demma.enabled=false -Dorson.jar.location=\\tmp\\ochaloup\\ext
> {quote}
> You can check whole stacktrace from job on jenkins:
> - https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTS/view/JBossT...
> - https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTS/view/JBossT...
> Do you think that you could check 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
10 years, 8 months
[JBoss JIRA] (JBTM-49) Add web-based tool interfaces
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-49?page=com.atlassian.jira.plugin.sy... ]
Tom Jenkinson updated JBTM-49:
------------------------------
Hi Mike,
This issue was marked as "Resolved, Done" but there is no "Fix Version" specified. Please can you update the Jira with the version of the software where you fixed this? Also, can you then close the issue (assuming its not an in development version).
Thanks,
Tom
> Add web-based tool interfaces
> -----------------------------
>
> Key: JBTM-49
> URL: https://issues.jboss.org/browse/JBTM-49
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Tooling, XTS
> Reporter: Mark Little
> Assignee: Michael Musgrove
>
> We need to be able to monitor/manage transactions (particularly WS-Ts) via the web.
--
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
10 years, 8 months
[JBoss JIRA] (JBTM-1778) JBossTS qa testsuite fails on HP-UX
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1778?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1778:
--------------------------------
Hi Mike,
This issue was marked as "Resolved, Done" but there is no "Fix Version" specified. Please can you update the Jira with the version of the software where you fixed this? Also, can you then close the issue (assuming its not an in development version).
Thanks,
Tom
> 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
> Attachments: jstack-3091
>
>
> 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
10 years, 8 months