June 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1382) QA build does not archive test group summary files

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1382?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1382: ----------------------------------- Status: Pull Request Sent (was: Reopened) Git Pull Request: https://github.com/jbosstm/narayana/pull/321 (was: https://github.com/jbosstm/narayana/pull/200) > 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: 4.17.5, 5.0.0.M2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1382) QA build does not archive test group summary files

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1382?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1382: ----------------------------------- Git Pull Request: https://github.com/jbosstm/narayana/pull/200, https://github.com/jbosstm/narayana/pull/321 (was: https://github.com/jbosstm/narayana/pull/321) > 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: 4.17.5, 5.0.0.M2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1498) Update all quickstarts to use new APIs provided by TXFramework

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1498?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-1498: ---------------------------------------- Paul, is this now out of date? If not the description should be something like "add a TXFramework version of all relevant quickstarts" > Update all quickstarts to use new APIs provided by TXFramework > -------------------------------------------------------------- > > Key: JBTM-1498 > URL: https://issues.jboss.org/browse/JBTM-1498 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Demonstrator, REST, TXFramework, XTS > Reporter: Paul Robinson > Assignee: Michael Musgrove > Fix For: 5.0.0.Final > > -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1336) DUPID detection for mysql in JTS mode does not work

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1336?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1336: ------------------------------------- Agreed, will raise a mysql issue. I inteded to wrap the return code in some kind of mysql test if feasible or leave code untouched, patch was for brevity. I will also add a known issue for it. > DUPID detection for mysql in JTS mode does not work > --------------------------------------------------- > > Key: JBTM-1336 > URL: https://issues.jboss.org/browse/JBTM-1336 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTS > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.0.0.M4 > > Attachments: JBTM-1336.patch > > Original Estimate: 3 days > Time Spent: 1 day > Remaining Estimate: 2 days > > Mysql does not send errorcode of XAException.XAER_DUPID, it sends 0. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1337) Use the node name if it is set, rather than the host name to construct Uid

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1337?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-1337. --------------------------------- Fix Version/s: (was: 5.0.0.Final) Resolution: Rejected > Use the node name if it is set, rather than the host name to construct Uid > -------------------------------------------------------------------------- > > Key: JBTM-1337 > URL: https://issues.jboss.org/browse/JBTM-1337 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > > Node name is going to give us guaranteed uniqueness for transaction managers, we could use node name instead of hostname and pid. > Uid is generic, xa node name is part of XA, but they are both in ArjunaCore/arjuna/ so it should not pose any dependency issues. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1336) DUPID detection for mysql in JTS mode does not work

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1336?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1336: -------------------------------- Fix Version/s: 5.0.0.M4 (was: 5.0.0.Final) > DUPID detection for mysql in JTS mode does not work > --------------------------------------------------- > > Key: JBTM-1336 > URL: https://issues.jboss.org/browse/JBTM-1336 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTS > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.0.0.M4 > > Attachments: JBTM-1336.patch > > Original Estimate: 3 days > Time Spent: 1 day > Remaining Estimate: 2 days > > Mysql does not send errorcode of XAException.XAER_DUPID, it sends 0. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1672) disable multiple plugins from eap6 profile

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1672?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1672: ------------------------------------- Also, build-helper is required to create the uber jars, if this is not possible, please can you raise a separate issue and we can keep this one as the "findbugs" issue which I can resolve assuming the tests pass? > disable multiple plugins from eap6 profile > ------------------------------------------ > > Key: JBTM-1672 > URL: https://issues.jboss.org/browse/JBTM-1672 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build System > Affects Versions: 4.17.4 > Reporter: Weinan Li > Assignee: Tom Jenkinson > > In EAP6 environment the dependencies of these plugins are not met: > {code} > * findbugs-maven-plugin > * maven-surefire-plugin > * build-helper-maven-plugin > * emma-maven-plugin > {code} > We need to exclude them from eap6 profile. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1672) disable multiple plugins from eap6 profile

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1672?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1672: ------------------------------------- Please can you clarify the reason to disable the maven-surefire-plugin? If it is still needed, please can you raise a separate Jira for this one? > disable multiple plugins from eap6 profile > ------------------------------------------ > > Key: JBTM-1672 > URL: https://issues.jboss.org/browse/JBTM-1672 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build System > Affects Versions: 4.17.4 > Reporter: Weinan Li > Assignee: Tom Jenkinson > > In EAP6 environment the dependencies of these plugins are not met: > {code} > * findbugs-maven-plugin > * maven-surefire-plugin > * build-helper-maven-plugin > * emma-maven-plugin > {code} > We need to exclude them from eap6 profile. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1672) disable multiple plugins from eap6 profile

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1672?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1672: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/323 I have addressed the findbugs issue in this pull request, I have previously addressed the emma one in a duplicate issue. > disable multiple plugins from eap6 profile > ------------------------------------------ > > Key: JBTM-1672 > URL: https://issues.jboss.org/browse/JBTM-1672 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build System > Affects Versions: 4.17.4 > Reporter: Weinan Li > Assignee: Tom Jenkinson > > In EAP6 environment the dependencies of these plugins are not met: > {code} > * findbugs-maven-plugin > * maven-surefire-plugin > * build-helper-maven-plugin > * emma-maven-plugin > {code} > We need to exclude them from eap6 profile. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1045) Add a persistent object into the recovery manager that we can talk to in the event of ONE after a resource has completed

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1045?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-1045. --------------------------------- Fix Version/s: (was: 5.0.0.Final) Resolution: Incomplete Description > Add a persistent object into the recovery manager that we can talk to in the event of ONE after a resource has completed > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBTM-1045 > URL: https://issues.jboss.org/browse/JBTM-1045 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: JTS > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > > add a persistent IOR into the RecoveryManager and that's used in the event we get the ONE for a basic resource. Kind of like a reverse RecoveryCoordinator (top-down RecoveryCoordinator) > You can embed lots of information into an IOR, so we can do this without changing any interfaces. -- 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, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues June 2013