Open dmitripivkine opened 6 years ago
We would like to enable https://github.com/eclipse/openj9/issues/3421 in 0.13. Do we need to fix this one by then? @pshipton
This is (I believe) an IBM cooked test that checks if an already started GC cycle finishes with (probably arbitrarily chosen) 30 sec even if there is no application activity. It's just a nice to have feature not imposed by specs.
There are more important ones to fix in CS world than this one, so I'm guessing, this won't be fixed for at least next few months.
Besides, it's affecting all platforms - I don't think it should prevent P from enabling CS.
JVMTI Test ghftm001.java initiates GC cycle and waiting (sleeping) for GC Cycle End event. However current implementation of Concurrent Scavenger does not force final STW Scavenge to complete cycle but expect it to be triggered by next Allocation Failure. So, because there is no further allocation in the test it reached timeout and failed eventually. Concurrent Scavenger should force final STW Scavenge as soon as concurrent phase is complete.