Bug #50826 mtr: allow a test to set its timeout
Submitted: 2 Feb 2010 10:46
Reporter: Guilhem Bichot Email Updates:
Status: Open Impact on me:
None 
Category:Tools: MTR / mysql-test-run Severity:S4 (Feature request)
Version: OS:Any
Assigned to: Assigned Account CPU Architecture:Any

[2 Feb 2010 10:46] Guilhem Bichot
Description:
It can happen that a certain test takes longer than the default mtr timeout (15 minutes), and this test cannot be split into shorter tests; then this test could be allowed to request a timeout higher than default.

How to repeat:
see BUG#50595: until we fix this bug in the long term, we would like to have it passing, which is possible if it requests a higher timeout.

Suggested fix:
http://lists.mysql.com/commits/98865
[5 Mar 2010 13:29] Guilhem Bichot
1) there is logic in mtr which does
"if --valgrind then increases default timeout" and the patch is not ready for this (it needs to increase the test's timeout too)
2) the solaris sparc32 debug_max machine does not run mtr tests anymore in pushbuild2, so there is less need for this patch