When jtreg executes a test in a separate process and that test times out it would be useful whenever possible to perform a thread dump the results of which are archived with the associated test report.
Such information is invaluable to verify if concurrent applications are deadlocked or waiting.
For example, regressions in a fork/join application may result in the application never completing and thus jtreg will timeout. Having a thread dump will allow a developer to verify if this is the case or not (e.g. a "livelock" or just taking too long to run).
Such information is invaluable to verify if concurrent applications are deadlocked or waiting.
For example, regressions in a fork/join application may result in the application never completing and thus jtreg will timeout. Having a thread dump will allow a developer to verify if this is the case or not (e.g. a "livelock" or just taking too long to run).
- duplicates
-
CODETOOLS-7900878 print stack traces for timed out tests
-
- Closed
-
- relates to
-
CODETOOLS-7900878 print stack traces for timed out tests
-
- Closed
-