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

[Roberto Castañeda Lozano]

On Fri, 16 Oct 2020 06:57:33 GMT, Roberto Castañeda Lozano <rcastanedalo 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.

This pull request has now been integrated.

Changeset: 98ec4a67
Author:    Roberto Castañeda Lozano <roberto.castaneda.lozano at oracle.com>
Committer: Tobias Hartmann <thartmann at openjdk.org>
URL:       https://git.openjdk.java.net/jdk/commit/98ec4a67
Stats:     34 lines in 2 files changed: 21 ins; 3 del; 10 mod

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

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.

Reviewed-by: kvn, thartmann

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

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