[jbossts-issues] [JBoss JIRA] (JBTM-1211) Fix qa suite failure: org.jboss.jbossts.qa.junit.testgroup.TestGroup_jtsremote

Michael Musgrove (JIRA) jira-events at lists.jboss.org
Fri Dec 14 10:20:17 EST 2012

    [ https://issues.jboss.org/browse/JBTM-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741508#comment-12741508 ] 

Michael Musgrove commented on JBTM-1211:

This is another timeout problem (the deadlock condition looks like it is now fixed). I could increase the timeout but since the test does not fail often I am tempted to just mark it as will not fix. But as soon as the failure recurs the JIRA will be reopened so it is Catch 22. What is the rationale for marking the fix for 4.17.4.

My proposal is to mark it as fix for 5.0.0.M2 only and then close as will not fix. Then if it gets re-opened I will review it again.
> Fix qa suite failure: org.jboss.jbossts.qa.junit.testgroup.TestGroup_jtsremote
> ------------------------------------------------------------------------------
>                 Key: JBTM-1211
>                 URL: https://issues.jboss.org/browse/JBTM-1211
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: JTS, Testing, Transaction Core
>    Affects Versions: 4.16.4
>            Reporter: Paul Robinson
>            Assignee: Michael Musgrove
>             Fix For: 4.17.4, 5.0.0.M2
>         Attachments: jbossts-narayana-java6-ipv6-dualstack.57.tar, jtsremote(1).zip, jtsremote.zip
> See:
> {code}
> Running org.jboss.jbossts.qa.junit.testgroup.TestGroup_jtsremote
>     [junit] Tests run: 9, Failures: 1, Errors: 0, Time elapsed: 169.235 sec
> {code}

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

More information about the jbossts-issues mailing list