From 10b80ccca678db057f64cb982844fe0080667261 Mon Sep 17 00:00:00 2001 From: Staffan Larsen Date: Mon, 17 Sep 2012 12:40:33 +0200 Subject: [PATCH] 7198849: Make javax/management/remote/mandatory/notif/ListenerScaleTest.java less timing sensitive Reviewed-by: alanb --- .../management/remote/mandatory/notif/ListenerScaleTest.java | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/jdk/test/javax/management/remote/mandatory/notif/ListenerScaleTest.java b/jdk/test/javax/management/remote/mandatory/notif/ListenerScaleTest.java index 4a278c39cb0..b6cd2999bb1 100644 --- a/jdk/test/javax/management/remote/mandatory/notif/ListenerScaleTest.java +++ b/jdk/test/javax/management/remote/mandatory/notif/ListenerScaleTest.java @@ -45,7 +45,7 @@ * * As usual with timing-sensitive tests, we could potentially get * sporadic failures. We fail if the ratio of the time with many - * MBeans to the time with just one MBean is more than 100. With the + * MBeans to the time with just one MBean is more than 500. With the * fix in place, it is usually less than 1, presumably because some * code was being interpreted during the first measurement but had * been compiled by the second. @@ -176,7 +176,7 @@ public class ListenerScaleTest { long manyMBeansTime = timeNotif(mbs); System.out.println("Time with many MBeans: " + manyMBeansTime + "ns"); double ratio = (double) manyMBeansTime / singleMBeanTime; - if (ratio > 100.0) + if (ratio > 500.0) throw new Exception("Failed: ratio=" + ratio); System.out.println("Test passed: ratio=" + ratio); }