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

[Nils Eliasson]

On Wed, 4 Nov 2020 21:08:30 GMT, Igor Ignatyev <iignatyev at openjdk.org> wrote:

> > ... In normal mode 6500 iterations of CodeCacheStressRunner was performed in 30 sec, with -Xcomp only 250. But in total compiles -Xcomp had 30% less compilations...
> 
> would it make sense to update `CodeCacheStressRunner` and/or individual tests to count iterations and have a reasonable (test-specific?) threshold below which a test isn't considered passed, but instead considered skipped (ie throws `jtreg.SkippedException`). this way we would know if tests run enough iterations in the allocated amount of time, and if they don't in some configuration, we will have data to make proper decision on either increasing time budget, decreasing threshold, or excluding configurations.
> 
> -- Igor

I experimented with couting the CodeCaceStressRunner iterations but the different tests have completely different profiles and the variants are many - 4 tests, 2 modes (Xcomp) that all need separate values.

I would like to see that we added thread dumps and core files on timeouts. Then we can experiment with lower timeouts since it will be possible to diagnose them quickly.

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

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