This test fails occasionally, and can be tuned to avoid most of the failures ever seen.
It exists to check that notification work does not scale linearly with number of MBeans, so it calculates a ratio of the time taken with one, and with 20,000 MBeans. We should increase point at which that calculated ratio is considered a failure. I chose 2500 here as it solves most of the failures that I think have ever been reported with the test, without being too forgiving that we ignore a serious slowdown in future. ------------- Commit messages: - 8313355: javax/management/remote/mandatory/notif/ListenerScaleTest.java failed with "Exception: Failed: ratio=792.2791601423487" Changes: https://git.openjdk.org/jdk/pull/16761/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=16761&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8313355 Stats: 4 lines in 1 file changed: 2 ins; 0 del; 2 mod Patch: https://git.openjdk.org/jdk/pull/16761.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/16761/head:pull/16761 PR: https://git.openjdk.org/jdk/pull/16761
