December 2015 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2203) Remove ReentrantLock from StateManager

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2203?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2203: -------------------------------- Forum Reference: https://developer.jboss.org/thread/242267 (was: https://community.jboss.org/message/879212) > Remove ReentrantLock from StateManager > -------------------------------------- > > Key: JBTM-2203 > URL: https://issues.jboss.org/browse/JBTM-2203 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTA > Affects Versions: 5.0.2 > Reporter: Michael Musgrove > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > Remove unused lock from StateManager, and add the access methods to LockManager instead -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2561) XTS code coverage failures

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2561?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2561: ------------------------------------- Is this one related: http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/263/console {quote} [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7:run (prepare-reports) on project narayana-code-coverage: An Ant BuildException has occured: /home/hudson/workspace/narayana-codeCoverage/XTS/localjunit/disabled-context-propagation/target/coverage-reports does not exist. [ERROR] around Ant part ...<report>... @ 6:11 in /home/hudson/workspace/narayana-codeCoverage/code-coverage/target/antrun/build-main.xml {quote} > XTS code coverage failures > -------------------------- > > Key: JBTM-2561 > URL: https://issues.jboss.org/browse/JBTM-2561 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > XTS tests fail to start on CI nodes when code coverage testing is enabled. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2553) Investigate the test with byteman do not work with the jacoco

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2553?page=com.atlassian.jira.plugin.... ] Amos Feng commented on JBTM-2553: --------------------------------- yeah, $0 works in the fail2pc.btm but it looks like the $this does work in the commitMarkableResourceFailAfterCommit.btm {code} RULE Fail first phase2Commit CLASS com.arjuna.ats.arjuna.coordinator.BasicAction METHOD doCommit AT EXIT BIND NOTHING IF readCounter("phase2commit") == 0 DO debug("Called"), incrementCounter("phase2commit"); com.arjuna.ats.arjuna.coordinator.ActionManager.manager().remove($this.get_uid()); throw new Error(); ENDRULE RULE Return not inflight CLASS com.arjuna.ats.internal.arjuna.recovery.AtomicActionRecoveryModule METHOD isTransactionInMidFlight AT ENTRY BIND NOTHING IF TRUE DO RETURN false; ENDRULE {code} The "Fail first phase2Commit" is triggered but the "Return not inflight" does not been installed. The other issue is that the jacoco could change the ordering of the elements in the recordList as the first XAResource is not the one expected. you can see the failure with running {code} ./build.sh -f ArjunaJTA/jta/pom.xml clean test -Dtest=TestCommitMarkableResourceFailActivate -Dorg.jboss.byteman.verbose -PcodeCoverage {code} > Investigate the test with byteman do not work with the jacoco > ------------------------------------------------------------- > > Key: JBTM-2553 > URL: https://issues.jboss.org/browse/JBTM-2553 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Testing > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2553) Investigate the test with byteman do not work with the jacoco

by Andrew Dinn (JIRA)

[ https://issues.jboss.org/browse/JBTM-2553?page=com.atlassian.jira.plugin.... ] Andrew Dinn commented on JBTM-2553: ----------------------------------- Hi Tom, One reason I know why this is so complex is that I found out that the latest version of Byteman is subject to the same issue i.e. it also shifts the start offset of this and parameter variables when it injects AT ENTRY (I have not yet found a test case for it but I think I will be able to reproduce the error Amos has seen by injecting multiple AT ENTRY rules into the same method). I have made several different attempts to fix the problem but so far none of them has worked. I'll continue to pursue this matter and let you know when I get something I can offer to the Jacoco team. As you say, the simple workaround is indeed to disable Byteman tests when checking coverage. However, there is a better alternative -- modify the affected rules so that they reference this and/or parameters using the indexed parameter syntax $0, $1 etc. This is slightly less readable but does allow the tests can be included in the coverage analysis. giving a much more realistic assessment of test coverage for some parts of the code (e.g. crash recovery). > Investigate the test with byteman do not work with the jacoco > ------------------------------------------------------------- > > Key: JBTM-2553 > URL: https://issues.jboss.org/browse/JBTM-2553 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Testing > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2553) Investigate the test with byteman do not work with the jacoco

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2553?page=com.atlassian.jira.plugin.... ] Tom Jenkinson edited comment on JBTM-2553 at 12/2/15 5:11 AM: -------------------------------------------------------------- Thanks for the detailed explanation Andrew - it certainly sounds a complex issue. Do you know of any other coverage frameworks that Byteman might interoperate with today? If not we can just disable the byteman tests under coverage testing. If you do get a Jacoco issue reference please can you let us know so we can reference it here? Thanks again! was (Author: tomjenkinson): Thanks for the detailed explanation Andrew - it certainly sounds a complex issue. Do you know of any other coverage frameworks that Byteman might interoperate with today? If not we can just disable it. If you do get a Jacoco issue reference please can you let us know so we can reference it here? Thanks again! > Investigate the test with byteman do not work with the jacoco > ------------------------------------------------------------- > > Key: JBTM-2553 > URL: https://issues.jboss.org/browse/JBTM-2553 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Testing > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2553) Investigate the test with byteman do not work with the jacoco

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2553?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2553: ------------------------------------- Thanks for the detailed explanation Andrew - it certainly sounds a complex issue. Do you know of any other coverage frameworks that Byteman might interoperate with today? If not we can just disable it. If you do get a Jacoco issue reference please can you let us know so we can reference it here? Thanks again! > Investigate the test with byteman do not work with the jacoco > ------------------------------------------------------------- > > Key: JBTM-2553 > URL: https://issues.jboss.org/browse/JBTM-2553 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Testing > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2572) Enable code coverage for the rest of the Arquillian tests

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2572?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2572: ---------------------------------- Parent: JBTM-2115 Issue Type: Sub-task (was: Task) > Enable code coverage for the rest of the Arquillian tests > --------------------------------------------------------- > > Key: JBTM-2572 > URL: https://issues.jboss.org/browse/JBTM-2572 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTA, REST > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2572) Enable code coverage for the rest of the Arquillian tests

by Gytis Trikleris (JIRA)

Gytis Trikleris created JBTM-2572: ------------------------------------- Summary: Enable code coverage for the rest of the Arquillian tests Key: JBTM-2572 URL: https://issues.jboss.org/browse/JBTM-2572 Project: JBoss Transaction Manager Issue Type: Task Components: JTA, REST Reporter: Gytis Trikleris Assignee: Gytis Trikleris Fix For: 5.next -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2561) XTS code coverage failures

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2561?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2561: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > XTS code coverage failures > -------------------------- > > Key: JBTM-2561 > URL: https://issues.jboss.org/browse/JBTM-2561 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > XTS tests fail to start on CI nodes when code coverage testing is enabled. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2517) Update the Narayana Release Process doc to include performance figures

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2517?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2517: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/performance/pull/29 > Update the Narayana Release Process doc to include performance figures > ---------------------------------------------------------------------- > > Key: JBTM-2517 > URL: https://issues.jboss.org/browse/JBTM-2517 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Performance Testing, Release Process > Affects Versions: 5.2.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > Include a description in the NRP document of how to blog about performance figures when releasing a new version of Narayana -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues December 2015