Bug 1096552 - RetryRule incompatible with JUnit Timeout
Summary: RetryRule incompatible with JUnit Timeout
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Zanata
Classification: Retired
Component: Maintainability
Version: development
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Damian Jansen
QA Contact: Zanata-QA Mailling List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-12 01:18 UTC by Damian Jansen
Modified: 2015-07-31 01:23 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-07-31 01:23:21 UTC
Embargoed:

Attachments (Terms of Use)

Description Damian Jansen 2014-05-12 01:18:46 UTC 
Description of problem:
The test framework's Timeout rule is not compatible with the RetryRule. Tests become unstable in that if a Retry occurs, the tests execute for 5 minutes regardless of actual run time.

Version-Release number of selected component (if applicable):
dev

How reproducible:
CI test indicators
Comment 1 Sean Flanigan 2015-04-17 05:09:59 UTC 
Perhaps we should re-evaluate this now that RetryRule is (almost) gone.  (We still seem to have a reference in TranslationHistoryTest, but with retries = 0.)

Timeouts can also be enforced by failsafe, which might make them less likely to interfere with debugging (especially if we configure Maven to disable the timeout when debugging).

http://maven.apache.org/surefire/maven-failsafe-plugin/integration-test-mojo.html#forkedProcessTimeoutInSeconds
Comment 2 Zanata Migrator 2015-07-31 01:23:21 UTC 
Migrated; check JIRA for bug status: http://zanata.atlassian.net/browse/ZNTA-476
Note You need to log in before you can comment on or make changes to this bug.