RFR: 8322987: Remove gc/stress/gclocker/TestGCLocker* since they always fail with OOME

Thomas Schatzl tschatzl at openjdk.org
Tue Jan 9 10:01:30 UTC 2024


Hi all,

  please review this change that removes the obsolete and ever-problemlisted `gc/stress/TestGCLocker*` tests.

The test tries to verify JNI by filling the heap, causing GCs, but always OOME'ing because the parameters to tune this behavior are too hard to get right for every case and every collector.

GCLocker functionality is already being tested with other tests like gc/TestJNICriticalStressTest, gc/cslocker/TestCSLocker, vmTestbase/gc/lock/*, other tests that incidentally use JNI and collector specific JNI tests (e.g. gc/g1/pinnedObjs/*).

Fwiw, the test also fails when replacing the JNI code by equivalent Java code i.e. not causing gclocker gcs.

Given all this I think removing these tests is just fine.

Thanks,
  Thomas

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

Commit messages:
 - 8322987

Changes: https://git.openjdk.org/jdk/pull/17322/files
 Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=17322&range=00
  Issue: https://bugs.openjdk.org/browse/JDK-8322987
  Stats: 448 lines in 7 files changed: 0 ins; 448 del; 0 mod
  Patch: https://git.openjdk.org/jdk/pull/17322.diff
  Fetch: git fetch https://git.openjdk.org/jdk.git pull/17322/head:pull/17322

PR: https://git.openjdk.org/jdk/pull/17322


More information about the hotspot-gc-dev mailing list