test/hotspot/jtreg/serviceability/jvmti/HeapMonitor/MyPackage/HeapMonitorStatArrayCorrectnessTest.java
--- a/test/hotspot/jtreg/serviceability/jvmti/HeapMonitor/MyPackage/HeapMonitorStatArrayCorrectnessTest.java Tue Jul 17 17:52:03 2018 -0700
+++ b/test/hotspot/jtreg/serviceability/jvmti/HeapMonitor/MyPackage/HeapMonitorStatArrayCorrectnessTest.java Tue Jul 17 19:59:38 2018 -0700
@@ -26,7 +26,7 @@
/**
* @test
* @build Frame HeapMonitor
- * @summary Verifies the JVMTI Heap Monitor rate when allocating arrays.
+ * @summary Verifies the JVMTI Heap Monitor interval when allocating arrays.
* @compile HeapMonitorStatArrayCorrectnessTest.java
* @run main/othervm/native -agentlib:HeapMonitorTest MyPackage.HeapMonitorStatArrayCorrectnessTest
*/
@@ -58,7 +58,7 @@
// 111 is as good a number as any.
final int samplingMultiplier = 111;
- HeapMonitor.setSamplingRate(samplingMultiplier * currentSize);
+ HeapMonitor.setSamplingInterval(samplingMultiplier * currentSize);
allocate(currentSize);
@@ -79,8 +79,8 @@
expected /= samplingMultiplier;
// 10% error ensures a sanity test without becoming flaky.
- // Flakiness is due to the fact that this test is dependent on the sampling rate, which is a
- // statistical geometric variable around the sampling rate. This means that the test could be
+ // Flakiness is due to the fact that this test is dependent on the sampling interval, which is a
+ // statistical geometric variable around the sampling interval. This means that the test could be
// unlucky and not achieve the mean average fast enough for the test case.
if (!HeapMonitor.statsHaveExpectedNumberSamples((int) expected, 10)) {
throw new RuntimeException("Statistics should show about " + expected + " samples.");