RFR: 8254805: compiler/debug/TestStressCM.java is still failing

[Roberto Castañeda Lozano]

On Fri, 16 Oct 2020 06:58:18 GMT, Roberto Castañeda Lozano <github.com+8792647+robcasloz at openjdk.org> wrote:

>> Use the code motion trace produced by `TraceOptoPipelining` (excluding traces of stubs) to assert that two compilations
>> with the same seed cause `StressLCM` and `StressGCM` to take the same randomized decisions. Previously, the entire
>> output produced by `PrintOptoStatistics` was used instead, which has shown to be too fragile. Also, disable inlining in
>> both `TestStressCM.java` and the similar `TestStressIGVN.java` to prevent flaky behavior, and run both tests for ten
>> different seeds to improve coverage.
>
> Use the code motion trace produced by TraceOptoPipelining (excluding traces of
> stubs) to assert that two compilations with the same seed cause StressLCM and
> StressGCM to take the same randomized decisions. Previously, the entire output
> produced by PrintOptoStatistics was used instead, which has shown to be too
> fragile. Also, disable inlining in both TestStressCM.java and the similar
> TestStressIGVN.java to prevent flaky behavior, and run both tests for ten
> different seeds to improve coverage.

Tested by running `TestStressCM.java` and `TestStressIGVN.java` 100 times each on windows-x64, linux-x64,
linux-aarch64, and macosx-x64 (all debug).

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

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