RFR: 8253877: gc/g1/TestGCLogMessages.java fails - missing "Evacuation failure" message
Stefan Johansson
sjohanss at openjdk.java.net
Fri Oct 16 11:28:10 UTC 2020
On Fri, 16 Oct 2020 09:21:36 GMT, Thomas Schatzl <tschatzl at openjdk.org> wrote:
> Exactly the catch-OOME approach seemed too error-prone. We may not recover from the OOME handler.
I agree, trying to recover from OOME is very error-prone. In this case since the test is starting in its own process it
might be fine to just let it exit with an OOME. We would have to change the check for exit-code 0, but I think it
should work.
Not saying this is a better approach, just threw it out here :) Again, I'm good with the change you propose.
-------------
PR: https://git.openjdk.java.net/jdk/pull/624
More information about the hotspot-gc-dev
mailing list