[jbossts-issues] [JBoss JIRA] (JBTM-939) Fix intermittant qa suite failure: org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery02_2
Michael Musgrove (JIRA)
jira-events at lists.jboss.org
Mon Oct 29 07:21:03 EDT 2012
[ https://issues.jboss.org/browse/JBTM-939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12729725#comment-12729725 ]
Michael Musgrove commented on JBTM-939:
---------------------------------------
That last failure was in CrashRecovery02_2_Test28 on hoboken (the other jobs have gone). The original fix was for test CrashRecovery02_2_Test31. So the question is do we keep extending timeouts for specific tests or do we extend the timeout for all tests in group CrashRecovery02_2? What do you think? If we go for extend timeout for specific tests then TEST-org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery02_2.txt tells us which test failed.
> Fix intermittant qa suite failure: org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery02_2
> ---------------------------------------------------------------------------------------------------
>
> Key: JBTM-939
> URL: https://issues.jboss.org/browse/JBTM-939
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Testing
> Reporter: Tom Jenkinson
> Assignee: Michael Musgrove
> Priority: Minor
> Fix For: 5.0.0.M2, 4.17.3
>
> Attachments: crashrecovery02_2.tgz
>
>
> Assuming failure in test rather than failed test:
> >>>>> org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery02_2
> >>>>> [junit] Tests run: 50, Failures: 1, Errors: 0, Time elapsed:
--
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