Bug #76296 Test timeout but no stack trace on windows
Submitted: 12 Mar 2015 15:12 Modified: 24 Nov 2016 14:38
Reporter: Sven Sandberg Email Updates:
Status: Closed Impact on me:
None 
Category:Tools: MTR / mysql-test-run Severity:S7 (Test Cases)
Version:5.6 OS:Any
Assigned to: CPU Architecture:Any

[12 Mar 2015 15:12] Sven Sandberg
Description:
When a test times out, we need a stack trace in order to debug it. We usually get this on Linux, but apparently not on Windows.

Except when the test is too slow, a timeout is most likely due to a deadlock. A stack trace would help to find out. With no stack trace it's impossible to analyze the bug.

How to repeat:
See any test run on windows, e.g. http://fimafeng11.no.oracle.com:8080/job/reviews-windows-5.1-5.5-5.6/2459/consoleText
or http://fimafeng11.no.oracle.com:8080/job/reviews-windows-5.1-5.5-5.6/2460/consoleText
[24 Nov 2016 14:38] Paul DuBois
Posted by developer:
 
Fixed in 8.0.1.

Work was done for test suite. No changelog entry needed.