Integrated: 8318668: java/lang/management/MemoryMXBean/CollectionUsageThreshold.java fails with Xcomp

[Ramkumar Sunderbabu]

On Sun, 17 Nov 2024 04:32:39 GMT, Ramkumar Sunderbabu <rsunderbabu at openjdk.org> wrote:

> Trivial change to exclude the test from running with Xcomp flag.
> 
> The test fails because the number of GCs as reported by the MXBean doesn't match the expected number. This is due to the additional GC happening due to CodeCache crossing its threshold.
> We could increase the code cache or restrict the specific compiler that fills the cache. But this will not completely eliminate the possibility as cache size could be overridden or the same failure can happen for a different compiler.
> 
> So, it is better to restrict the Xcomp flag as a whole.
> 
> Testing:
> Only local testing done as it is trivial change. One run with Xcomp and another without any flags.

This pull request has now been integrated.

Changeset: 162d66ad
Author:    Ramkumar Sunderbabu <rsunderbabu at openjdk.org>
Committer: Leonid Mesnik <lmesnik at openjdk.org>
URL:       https://git.openjdk.org/jdk/commit/162d66adacf71e500c85382a155c7449a4f9ba55
Stats:     2 lines in 1 file changed: 0 ins; 0 del; 2 mod

8318668: java/lang/management/MemoryMXBean/CollectionUsageThreshold.java fails with Xcomp

Reviewed-by: kevinw, lmesnik

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

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