May 2019 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3144) LRA TCK Test Failure

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3144?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Michael Musgrove created pull request #1449 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > LRA TCK Test Failure > -------------------- > > Key: JBTM-3144 > URL: https://issues.jboss.org/browse/JBTM-3144 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.5.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The TCK test TckTests.acceptCancelTest is failing consistently. The test needs to wait for a recovery pass but the upstream project (Microprofile LRA) where the test is defined was recently changed to use timeouts and I suspect the test is not waiting long enough for the recovery to occur. > TckTests.timeLimit has also been seen to fail (probably for the same reason) -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3144) LRA TCK Test Failure

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3144?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3144: ----------------------------------- Description: The TCK test TckTests.acceptCancelTest is failing consistently. The test needs to wait for a recovery pass but the upstream project (Microprofile LRA) where the test is defined was recently changed to use timeouts and I suspect the test is not waiting long enough for the recovery to occur. TckTests.timeLimit has also been seen to fail (probably for the same reason) was:The TCK test TckTests.acceptCancelTest is failing consistently. The test needs to wait for a recovery pass but the upstream project (Microprofile LRA) where the test is defined was recently changed to use timeouts and I suspect the test is not waiting long enough for the recovery to occur. > LRA TCK Test Failure > -------------------- > > Key: JBTM-3144 > URL: https://issues.jboss.org/browse/JBTM-3144 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.5.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The TCK test TckTests.acceptCancelTest is failing consistently. The test needs to wait for a recovery pass but the upstream project (Microprofile LRA) where the test is defined was recently changed to use timeouts and I suspect the test is not waiting long enough for the recovery to occur. > TckTests.timeLimit has also been seen to fail (probably for the same reason) -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3144) LRA TCK Test Failure

by Michael Musgrove (Jira)

Michael Musgrove created JBTM-3144: -------------------------------------- Summary: LRA TCK Test Failure Key: JBTM-3144 URL: https://issues.jboss.org/browse/JBTM-3144 Project: JBoss Transaction Manager Issue Type: Bug Components: LRA Affects Versions: 5.9.5.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next The TCK test TckTests.acceptCancelTest is failing consistently. The test needs to wait for a recovery pass but the upstream project (Microprofile LRA) where the test is defined was recently changed to use timeouts and I suspect the test is not waiting long enough for the recovery to occur. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3143) Enable ArjunaJTS/jts Narayana quickstart to be run as automated testcase

by Ondrej Chaloupka (Jira)

Ondrej Chaloupka created JBTM-3143: -------------------------------------- Summary: Enable ArjunaJTS/jts Narayana quickstart to be run as automated testcase Key: JBTM-3143 URL: https://issues.jboss.org/browse/JBTM-3143 Project: JBoss Transaction Manager Issue Type: Enhancement Components: Testing Reporter: Ondrej Chaloupka Assignee: Ondrej Chaloupka ArjunaJTS/jts is nor run as is not defined as {{<module>}} under {{ArjunaJTS]} quickstart folder. When activated there is no active test to be run. Renaming {{CallJTSCMTBean}} to {{CallJTSCMTTest}} makes the test to be launched but as the test does not define a way to deploy components ({{1}}, {{2}}) to WFLY server the test fails. Arquillian deployment is probably needed to get automatic WFLY startup and deploy. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3142) Upgrade to the latest parent pom (org.jboss:jboss-parent:35)

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3142?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Michael Musgrove created pull request #1447 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Upgrade to the latest parent pom (org.jboss:jboss-parent:35) > ------------------------------------------------------------ > > Key: JBTM-3142 > URL: https://issues.jboss.org/browse/JBTM-3142 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.9.5.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > Upgrade our top level pom parent to use the lates version of jboss-parent ((org.jboss:jboss-parent:35) -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3142) Upgrade to the latest parent pom (org.jboss:jboss-parent:35)

by Michael Musgrove (Jira)

Michael Musgrove created JBTM-3142: -------------------------------------- Summary: Upgrade to the latest parent pom (org.jboss:jboss-parent:35) Key: JBTM-3142 URL: https://issues.jboss.org/browse/JBTM-3142 Project: JBoss Transaction Manager Issue Type: Bug Components: Build System Affects Versions: 5.9.5.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next Upgrade our top level pom parent to use the lates version of jboss-parent ((org.jboss:jboss-parent:35) -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 12 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 May 2019