JDK-8253877 : gc/g1/TestGCLogMessages.java fails - missing "Evacuation failure" message
  • Type: Bug
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 16
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2020-09-30
  • Updated: 2022-10-10
  • Resolved: 2020-10-19
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 11 JDK 16
11.0.18-oracleFixed 16 b21Fixed
Related Reports
Blocks :  
JDK-8253413 - [REDO] [REDO] G1 incorrectly limiting young gen size when using the reserve can result in repeated full gcs
Relates :  
JDK-8248382 - gc/g1/TestGCLogMessages.java fails - missing "Evacuation failure" message
Description
Test gc/g1/TestGCLogMessages.java intermittently fail with 
Execution failed: `main' threw exception: java.lang.RuntimeException: '\[debug.*Evacuation Failure' missing from stdout/stderr
Comments
Fix request [11u] I backport this for parity with 11.0.18-oracle. No risk, only a test change. I had to do a simple resolve. Test passes. SAP nighlty testing passed.
08-10-2022
A pull request was submitted for review. URL: https://git.openjdk.org/jdk11u-dev/pull/1400 Date: 2022-10-07 19:31:00 +0000
07-10-2022
Changeset: cd66e0f2 Author: Thomas Schatzl <tschatzl@openjdk.org> Date: 2020-10-19 11:40:58 +0000 URL: https://git.openjdk.java.net/jdk/commit/cd66e0f2
19-10-2020
Almost sure this is an issue with the introduction of the young gen sizing fixes that were later retracted, i.e. the same as JDK-8248382. Still seems to be a problem with the test. This should be checked again before re-introduction of JDK-8253413. At least with current JDK I can't reproduce after 2k iterations.
06-10-2020
Most likely because after JDK-8240556 the method to force an evacuation failure got unreliable. So labelling this as testbug for now.
02-10-2020