The test nsk/monitoring/MemoryPoolMBean/isCollectionUsageThresholdExceeded/isexceeded003 was on the ProblemList when open-sourced ( 8199375 ).

The test in question was noted to fail, but that was many years ago. Logs of failures from so many years ago are no longer available.

A historical closed issue JDK-8153598 has a suggestion in 2016 to unproblemlist it.

The isCollectionUsageThresholdExceeded/isexceeded00* tests all test well, e.g. 50 passes in each platform, we should unproblemlist this.


The original bug 8153598 for nsk/monitoring/MemoryPoolMBean/isCollectionUsageThresholdExceeded/isexceeded003 contains comments that were possibly meant to be in 8198668 for MemoryPoolMBean/isUsageThresholdExceeded/isexceeded001/TestDescription.java
as they mention that test by name, and not isCollectionUsageThresholdExceeded.

i.e. isCollectionUsageThresholdExceeded may have been unfairly/mistakenly labelled with more failures than really happened.


This test has some of the same issues as 8198668, such as making an allocation and watching for changes in a memory pool being a flawed idea. However it does give a sanity check, i.e. that a pool does not cross a threshold, and does not claim to cross a threshold. It checks for a correct UnsupportedOperationException if !monitor.isCollectionThresholdSupported(pool)).

Also this problemlist change only covers 1 of 5 tests, there are isexceeded001 to 005 inclusive, only 003 is problemlisted.