[
https://issues.apache.org/jira/browse/HBASE-8303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell reopened HBASE-8303:
-----------------------------------
This also affects 0.94: TestConstraint (10 s), TestTimeoutExceptionInjector (1
s), TestSnapshotFromMaster (15 s), TestAssignmentManager (5 s), TestThreads (6
s), TestSnapshotFromAdmin (10 s), TestFlushSnapshotFromClient (15 s),
TestPBOnWritableRpc (10 s), TestCallQueue (3 s), TestProcedure (1 s),
TestZKProcedureControllers (15 s), TestProcedureCoordinator (5 s, 1 s),
TestProcedureMember (1 s), TestHRegionBusyWait (2 s),
TestSplitTransactionOnCluster (20 s), TestZooKeeper (20 s).
Should we tackle this on this jira or open a new one?
> Increse the test timeout to 60s when they are less than 20s
> -----------------------------------------------------------
>
> Key: HBASE-8303
> URL: https://issues.apache.org/jira/browse/HBASE-8303
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.95.0
> Reporter: Nicolas Liochon
> Assignee: Nicolas Liochon
> Fix For: 0.98.0, 0.95.1
>
> Attachments: 8303.v1.patch, 8303.v1.patch
>
>
> Short test timeouts are dangerous because:
> - if the test is executed in the same jvm as another, GC, thread priority
> can play a role
> - we don't know the machine used to execute the tests, nor what's running on
> it;.
> For this reason, a test timeout of 60s allows us to be on the safe side.
--
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
