JDK-8342580 : GenShen: TestChurnNotifications fails executing in unintended test-id modes with ShenandoahGCMode=generational
  • Type: Sub-task
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: repo-shenandoah
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2024-10-18
  • Updated: 2024-12-13
  • Resolved: 2024-10-23
Related Reports
Relates :  
Description
When run with `ShenandoahGCMode=generational` TestChurnNotifications fails in certain modes. One solution is to explicitly mark non-generational mode tests to state that they should not run if generational mode is explicitly set. While it is not clear to this author if the other ShenandoahGCHeuristics settings make sense with generational mode, if those are tested then the mem.pool system property should be set. It would, however, be ideal if the test would use the right memory pool to use without having to specify it in the test.
Comments
A pull request was submitted for review. Branch: master URL: https://git.openjdk.org/shenandoah-jdk21u/pull/143 Date: 2024-12-11 18:48:01 +0000
11-12-2024

Disable testing with explicit heuristics settings when testing with GenShen. We discovered that GenShen silently ignores the heuristics setting and uses its own heuristics. The latter is correct, but emitting a warning when something else is explicitly selected may be a more user-friendly experience. That will be fixed in a separate ticket which will be linked here. (Code to check for this may have been lost in some GenShen refactoring; see linked ticket JDK-8342640 ).
22-10-2024

A pull request was submitted for review. Branch: master URL: https://git.openjdk.org/shenandoah/pull/520 Date: 2024-10-18 21:33:10 +0000
18-10-2024

The right way to fix this is still being discussed, but a draft PR is available for perusal at: https://github.com/openjdk/shenandoah/compare/master...ysramakrishna:shenandoah:test_requires
18-10-2024