Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Plain View
Hadoop >> mail # dev >> Re: Policy on adding timeouts to tests

Chris Nauroth 2014-04-15, 18:38
Karthik Kambatla 2014-04-15, 20:21
Steve Loughran 2014-04-16, 09:12
Tsuyoshi OZAWA 2014-04-16, 17:52
Andrew Wang 2014-04-16, 18:44
Vinod Kumar Vavilapalli 2014-04-17, 04:24
Copy link to this message
Re: Policy on adding timeouts to tests
The most common mistake is making incorrect assumptions on test/component
run-time. We often forget how slower/faster things can be on different
platforms and how the load on the machine at the time of test execution
affect the run time.  If not sure, leave it to surefire. If things run
generally slow on certain environment and the 10 min timeout generates
many false positives, it is easier to adjust. But early detection of
failures is still preferred, if possible.

Some are using timeout for validating performance in unit tests.  This
should not be done in unit tests. Also, many test issues have been due to
incorrect assumptions on the ordering/timing of events and resulting state
updates. These test cases usually timeout waiting for certain state to be


On 4/16/14, 11:24 PM, "Vinod Kumar Vavilapalli" <[EMAIL PROTECTED]> wrote: