RFR: 8255011: [TESTBUG] UnexpectedDeoptimizationAllTest.java timed out

[Nils Eliasson]

On Wed, 4 Nov 2020 22:48:06 GMT, Igor Ignatyev <iignatyev at openjdk.org> wrote:

> we actually do that since JDK 9, [JEP 279](https://bugs.openjdk.java.net/browse/JDK-8075621) added the failure handler which runs many things including `jstack`, `gdb -ex thread apply all backtrace` (or its equivalent) to get java and native thread dumps and `kill -ABRT` to generate core files on timeouts. however b/c it's run concurrently to a timed out process, you don't always get the data. so I'm wondering what you meant.

That has completely passed me by. I must look into it.

Regarding the test:
I think 60 secs is plenty of time for this test, especially since it runs multiple times. If there is a deadlock - the test will timeout regardless of timeout time. Adding some workload measurement would be nice - but not worth the time in my opinion.

-------------

PR: https://git.openjdk.java.net/jdk/pull/1030