Integrated: 8342580: GenShen: TestChurnNotifications fails executing in unintended test-id modes with ShenandoahGCMode=generational

Y. Srinivas Ramakrishna ysr at openjdk.org
Wed Oct 23 17:23:49 UTC 2024


On Fri, 18 Oct 2024 21:33:10 GMT, Y. Srinivas Ramakrishna <ysr at openjdk.org> wrote:

> Generational mode should not be tested with explicit heuristics settings, which are silently ignored. The test failed in these settings because it needs to be told which memory pool to check for notifications, which needs to be specified differently for generational. Ideally, we'd have the test figure this out rather than needing this to be explicitly specified. For now I just tightened the `@requires` clause to run only in the intended modes.
> 
> Related cleanups will follow separately (such as emitting a warning when an incompatible heuristics option is specified, code which may have been lost in a previous refactor). See details in the ticket.
> 
> **Testing** : tested with no specific collector, with Shenandoah, withGenShen, and with other collectors with test explicitly specified. As intended, in the first and second case 6 test-ids are run, in the thirdd case 1 test-id is run, and in the remaining cases, 0 test-ids are run.

This pull request has now been integrated.

Changeset: 49707080
Author:    Y. Srinivas Ramakrishna <ysr at openjdk.org>
URL:       https://git.openjdk.org/shenandoah/commit/49707080919c2edf42bef05911e60769aa13aa6d
Stats:     5 lines in 1 file changed: 0 ins; 0 del; 5 mod

8342580: GenShen: TestChurnNotifications fails executing in unintended test-id modes with ShenandoahGCMode=generational

Reviewed-by: wkemper, kdnilsen

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

PR: https://git.openjdk.org/shenandoah/pull/520


More information about the shenandoah-dev mailing list