February 2019 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3115) Make not running the LRA TCK testing the default

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3115?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3115: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Make not running the LRA TCK testing the default > ------------------------------------------------ > > Key: JBTM-3115 > URL: https://issues.jboss.org/browse/JBTM-3115 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.3.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The CI jobs are currently failing due to LRA TCK test failures. > I propose that we do not run the TCK by default by setting skipTests to true in the TCK pom -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3115) Make not running the LRA TCK testing the default

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3115?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Michael Musgrove created pull request #1417 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Make not running the LRA TCK testing the default > ------------------------------------------------ > > Key: JBTM-3115 > URL: https://issues.jboss.org/browse/JBTM-3115 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.3.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The CI jobs are currently failing due to LRA TCK test failures. > I propose that we do not run the TCK by default by setting skipTests to true in the TCK pom -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3115) Make not running the LRA TCK testing the default

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3115?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3115: ----------------------------------- Description: The CI jobs are currently failing due to LRA TCK test failures. I propose that we do not run the TCK by default by setting skipTests to true in the TCK pom was: The CI jobs are currently failing due to LRA TCK test failures. I propose that we move the tests into a separate profile so that it can be run on demand only. > Make not running the LRA TCK testing the default > ------------------------------------------------ > > Key: JBTM-3115 > URL: https://issues.jboss.org/browse/JBTM-3115 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.3.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The CI jobs are currently failing due to LRA TCK test failures. > I propose that we do not run the TCK by default by setting skipTests to true in the TCK pom -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3115) Make not running the LRA TCK testing the default

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3115?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3115: ----------------------------------- Summary: Make not running the LRA TCK testing the default (was: Move LRA TCK testing into a separate profile) > Make not running the LRA TCK testing the default > ------------------------------------------------ > > Key: JBTM-3115 > URL: https://issues.jboss.org/browse/JBTM-3115 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.3.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The CI jobs are currently failing due to LRA TCK test failures. > I propose that we move the tests into a separate profile so that it can be run on demand only. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3115) Temporarily disable LRA testing

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3115?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3115: ----------------------------------- Description: The CI jobs are currently failing due to LRA TCK test failures. I propose that we move the tests into a separate profile so that it can be run on demand only. was: The CI jobs are currently failing due to LRA TCK test failures. I propose that we disable testing by default until the TCK is stabilised. > Temporarily disable LRA testing > ------------------------------- > > Key: JBTM-3115 > URL: https://issues.jboss.org/browse/JBTM-3115 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.3.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The CI jobs are currently failing due to LRA TCK test failures. > I propose that we move the tests into a separate profile so that it can be run on demand only. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3115) Move LRA TCK testing into a separate profile

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3115?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3115: ----------------------------------- Summary: Move LRA TCK testing into a separate profile (was: Temporarily disable LRA testing) > Move LRA TCK testing into a separate profile > -------------------------------------------- > > Key: JBTM-3115 > URL: https://issues.jboss.org/browse/JBTM-3115 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.3.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The CI jobs are currently failing due to LRA TCK test failures. > I propose that we move the tests into a separate profile so that it can be run on demand only. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3115) Temporarily disable LRA testing

by Michael Musgrove (Jira)

Michael Musgrove created JBTM-3115: -------------------------------------- Summary: Temporarily disable LRA testing Key: JBTM-3115 URL: https://issues.jboss.org/browse/JBTM-3115 Project: JBoss Transaction Manager Issue Type: Bug Components: LRA Affects Versions: 5.9.3.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next The CI jobs are currently failing due to LRA TCK test failures. I propose that we disable testing by default until the TCK is stabilised. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3114) LRA module should depend on a specific snapshot build

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3114?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-3114: -------------------------------- Summary: LRA module should depend on a specific snapshot build (was: [5.9.4] LRA module should depend on a specific snapshot build) > LRA module should depend on a specific snapshot build > ----------------------------------------------------- > > Key: JBTM-3114 > URL: https://issues.jboss.org/browse/JBTM-3114 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.3.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > > The Narayana implementation of the LRA spec should depend on specific LRA API snapshot builds (since the LRA API is a moving target). > This problem has been fixed in JBTM-3091 and reintroduced in https://github.com/jbosstm/narayana/pull/1408/files#diff-14510da88f467b20.... > Current version of the implementation is running against latest build: > - api - 1.0-20190222.071200-278 > - tck - 1.0-20190222.071201-278 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3114) [5.9.4] LRA module should depend on a specific snapshot build

by Martin Stefanko (Jira)

[ https://issues.jboss.org/browse/JBTM-3114?page=com.atlassian.jira.plugin.... ] Martin Stefanko updated JBTM-3114: ---------------------------------- Fix Version/s: (was: 5.9.3.Final) > [5.9.4] LRA module should depend on a specific snapshot build > ------------------------------------------------------------- > > Key: JBTM-3114 > URL: https://issues.jboss.org/browse/JBTM-3114 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.3.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > > The Narayana implementation of the LRA spec should depend on specific LRA API snapshot builds (since the LRA API is a moving target). > This problem has been fixed in JBTM-3091 and reintroduced in https://github.com/jbosstm/narayana/pull/1408/files#diff-14510da88f467b20.... > Current version of the implementation is running against latest build: > - api - 1.0-20190222.071200-278 > - tck - 1.0-20190222.071201-278 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3114) [5.9.4] LRA module should depend on a specific snapshot build

by Martin Stefanko (Jira)

[ https://issues.jboss.org/browse/JBTM-3114?page=com.atlassian.jira.plugin.... ] Martin Stefanko reassigned JBTM-3114: ------------------------------------- Assignee: Martin Stefanko (was: Michael Musgrove) > [5.9.4] LRA module should depend on a specific snapshot build > ------------------------------------------------------------- > > Key: JBTM-3114 > URL: https://issues.jboss.org/browse/JBTM-3114 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.3.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > Fix For: 5.9.3.Final > > > The Narayana implementation of the LRA spec should depend on specific LRA API snapshot builds (since the LRA API is a moving target). > This problem has been fixed in JBTM-3091 and reintroduced in https://github.com/jbosstm/narayana/pull/1408/files#diff-14510da88f467b20.... > Current version of the implementation is running against latest build: > - api - 1.0-20190222.071200-278 > - tck - 1.0-20190222.071201-278 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 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 February 2019