Integrated: 8254027: gc/g1/TestHumongousConcurrentStartUndo.java failed with "'Concurrent Mark Cycle' missing from stdout/stderr"

[Thomas Schatzl]

On Tue, 6 Oct 2020 13:06:42 GMT, Thomas Schatzl <tschatzl at openjdk.org> wrote:

> Hi all,
> 
>   can I get reviews for this change to the test to verify concurrent mark/undo cycles to make it more stable?
> 
> In the failing scenario, the second concurrent cycle that would typically result in a complete concurrent mark would
> start with too few strongly reachable humongous objects, so instead g1 performs an Undo cycle, resulting in that
> message.  The changes make sure that if the second concurrent start pause starts there are always enough strongly
> reachable humongous objects there to disallow an undo cycle (because the reason we started the cycle has been
> allocation of that amount of humongous objects that are all guaranteed to be kept reachable).  Testing: could not
> reproduce the failure, but 2k runs on linux/aarch64 did not show an issue.

This pull request has now been integrated.

Changeset: 894ec76c
Author:    Thomas Schatzl <tschatzl at openjdk.org>
URL:       https://git.openjdk.java.net/jdk/commit/894ec76c
Stats:     7 lines in 1 file changed: 6 ins; 0 del; 1 mod

8254027: gc/g1/TestHumongousConcurrentStartUndo.java failed with "'Concurrent Mark Cycle' missing from stdout/stderr"

Reviewed-by: sjohanss, kbarrett

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

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