June 2013 - jbossts-issues - Jboss List Archives

[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 resolved JBTM-1777. --------------------------------- Resolution: Done Reports now available here: http://172.17.131.2/view/Narayana+BlackTie/job/narayana-codeCoverage/last... and: http://172.17.131.2/view/Narayana+BlackTie/job/narayana-codeCoverage/last... > 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1786) Change to TMFAIL for an ABORT on a non-prepared TX

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/JBTM-1786?page=com.atlassian.jira.plugin.... ] Johnathon Lee updated JBTM-1786: -------------------------------- Git Pull Request: https://github.com/jbosstm/narayana/pull/342 > Change to TMFAIL for an ABORT on a non-prepared TX > -------------------------------------------------- > > Key: JBTM-1786 > URL: https://issues.jboss.org/browse/JBTM-1786 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTA > Affects Versions: 4.16.4 > Reporter: Johnathon Lee > Assignee: Johnathon Lee > > An ABORT on a non-prepared TX should be calling end with TMFAIL. > It's more efficient in that the RM can return an RB* code immediately and short circuit the rollback internally if it likes. More importantly though the RM is less likely to object that it's still running tx activity on another thread and the concurrent TMSUCCESS therefore makes no sense to it. > Also the XAResourceRecord.topLevelAbort code should immediately continue on to calling rollback on the resource despite the failed end(). -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1786) Change to TMFAIL for an ABORT on a non-prepared TX

by Johnathon Lee (JIRA)

Johnathon Lee created JBTM-1786: ----------------------------------- Summary: Change to TMFAIL for an ABORT on a non-prepared TX Key: JBTM-1786 URL: https://issues.jboss.org/browse/JBTM-1786 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA Affects Versions: 4.16.4 Reporter: Johnathon Lee Assignee: Johnathon Lee An ABORT on a non-prepared TX should be calling end with TMFAIL. It's more efficient in that the RM can return an RB* code immediately and short circuit the rollback internally if it likes. More importantly though the RM is less likely to object that it's still running tx activity on another thread and the concurrent TMSUCCESS therefore makes no sense to it. Also the XAResourceRecord.topLevelAbort code should immediately continue on to calling rollback on the resource despite the failed end(). -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1785) TXBridge quickstart does not exist in master

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-1785: ----------------------------------- Summary: TXBridge quickstart does not exist in master Key: JBTM-1785 URL: https://issues.jboss.org/browse/JBTM-1785 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Demonstrator, TxBridge Reporter: Tom Jenkinson Assignee: Paul Robinson Fix For: 5.0.0.M4 Maybe I missed something but the /TXBridge tree from 4.17 is no longer present in master? This could be related to JBTM-1469 but there is no reference there that the quickstart has been deleted from master that I can see? -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1784) TXBridge quickstart contains a reference to an artifact that should be brought in via its corresponding uber jar

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1784?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-1784. --------------------------------- Resolution: Done > TXBridge quickstart contains a reference to an artifact that should be brought in via its corresponding uber jar > ---------------------------------------------------------------------------------------------------------------- > > Key: JBTM-1784 > URL: https://issues.jboss.org/browse/JBTM-1784 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Documentation, TxBridge > Reporter: Tom Jenkinson > Assignee: Paul Robinson > Fix For: 4.17.5 > > > TXBridge/demo/service/pom.xml and TXBridge/demo/service/pom.xml both reference: > <groupId>org.jboss.jbossts.jta</groupId> > <artifactId>jta</artifactId> > When they should reference the uber jar: > <artifactId>narayana-jta</artifactId> > The uber jar is uploaded to maven central whereas the constituent jars are intermediary build artifacts. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1784) TXBridge quickstart contains a reference to an artifact that should be brought in via its corresponding uber jar

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-1784: ----------------------------------- Summary: TXBridge quickstart contains a reference to an artifact that should be brought in via its corresponding uber jar Key: JBTM-1784 URL: https://issues.jboss.org/browse/JBTM-1784 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation, TxBridge Reporter: Tom Jenkinson Assignee: Paul Robinson Fix For: 4.17.5 TXBridge/demo/service/pom.xml and TXBridge/demo/service/pom.xml both reference: <groupId>org.jboss.jbossts.jta</groupId> <artifactId>jta</artifactId> When they should reference the uber jar: <artifactId>narayana-jta</artifactId> The uber jar is uploaded to maven central whereas the constituent jars are intermediary build artifacts. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1778) JBossTS qa testsuite fails on HP-UX

by Ondřej Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-1778?page=com.atlassian.jira.plugin.... ] Ondřej Chaloupka edited comment on JBTM-1778 at 6/13/13 6:29 AM: ----------------------------------------------------------------- The results are all blue because I needed all the test being run. So I've redefined the junit task to not stop on failure. {code} sed 's/haltonfailure="yes"/haltonfailure="no"/' run-dtf-local.xml {code} You can check the console log file where the failures could be seen. Failures are consistent for all the configuration runs. What I forgot to mention before is that Test20 is not run (org.jboss.jbossts.qa.CurrentTests01.Test20) because it stacks the processing in some deadlock like scenario. So I remove it from the runs. was (Author: ochaloup): The results are all blue because I needed all the test being run. So I've redefined the junit task to not stop on failure. {code} sed s/haltonfailure="yes"/haltonfailure="no"/' run-dtf-local.xml {code} You can check the console log file where the failures could be seen. Failures are consistent for all the configuration runs. What I forgot to mention before is that Test20 is not run (org.jboss.jbossts.qa.CurrentTests01.Test20) because it stacks the processing in some deadlock like scenario. So I remove it from the runs. > 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1778) JBossTS qa testsuite fails on HP-UX

by Ondřej Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-1778?page=com.atlassian.jira.plugin.... ] Ondřej Chaloupka commented on JBTM-1778: ---------------------------------------- The results are all blue because I needed all the test being run. So I've redefined the junit task to not stop on failure. {code} sed s/haltonfailure="yes"/haltonfailure="no"/' run-dtf-local.xml {code} You can check the console log file where the failures could be seen. Failures are consistent for all the configuration runs. What I forgot to mention before is that Test20 is not run (org.jboss.jbossts.qa.CurrentTests01.Test20) because it stacks the processing in some deadlock like scenario. So I remove it from the runs. > 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1778) JBossTS qa testsuite fails on HP-UX

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1778?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-1778: ---------------------------------------- It looks like a spurious error since the configuration matrix for HP-UK is showing all blues > 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1780) Missing test for failures during the REST-AT volatile prepare phase

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1780?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1780: ----------------------------------- Comment: was deleted (was: Pull passed) > Missing test for failures during the REST-AT volatile prepare phase > ------------------------------------------------------------------- > > Key: JBTM-1780 > URL: https://issues.jboss.org/browse/JBTM-1780 > 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 > Priority: Minor > Fix For: 5.0.0.M4 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > There is code in the test participant (org.jboss.jbossts.star.test.BaseTest TransactionalResource#synchronizations) to fail the volatile prepare phase but org.jboss.jbossts.star.test.OptionalSpecTest does not exercise 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, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues June 2013