archive/jdk
1
0
Fork 0
mirror of https://github.com/openjdk/jdk.git synced 2025-09-15 08:34:30 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

8007890: [TESTBUG] JcmdWithNMTDisabled.java fails when invoked with NMT explicitly turned on

Browse source 
Wrapped the test in another layer process creation to avoid NMT being turned on.

Reviewed-by: coleenp, dcubed
This commit is contained in:
Christian Tornqvist 2014-03-27 22:36:08 +01:00
parent 472622d900
commit 0b0fdb97ce
1 changed files with 22 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

26
hotspot/test/runtime/NMT/JcmdWithNMTDisabled.java
View file

@ -26,10 +26,7 @@
* @key nmt jcmd
* @summary Verify that jcmd correctly reports that NMT is not enabled
* @library /testlibrary
* First run without enabling NMT
* @run main/othervm JcmdWithNMTDisabled
* Then run with explicitly disabling NMT, should not be any difference
* @run main/othervm -XX:NativeMemoryTracking=off JcmdWithNMTDisabled
* @run main JcmdWithNMTDisabled 1
*/
import com.oracle.java.testlibrary.*;
@ -39,6 +36,27 @@ public class JcmdWithNMTDisabled {
static String pid;
public static void main(String args[]) throws Exception {
// This test explicitly needs to be run with the exact command lines below, not passing on
// arguments from the parent VM is a conscious choice to avoid NMT being turned on.
if (args.length > 0) {
ProcessBuilder pb;
OutputAnalyzer output;
String testjdkPath = System.getProperty("test.jdk");
// First run without enabling NMT
pb = ProcessTools.createJavaProcessBuilder("-Dtest.jdk=" + testjdkPath, "JcmdWithNMTDisabled");
output = new OutputAnalyzer(pb.start());
output.shouldHaveExitValue(0);
// Then run with explicitly disabling NMT, should not be any difference
pb = ProcessTools.createJavaProcessBuilder("-Dtest.jdk=" + testjdkPath, "-XX:NativeMemoryTracking=off", "JcmdWithNMTDisabled");
output = new OutputAnalyzer(pb.start());
output.shouldHaveExitValue(0);
return;
}
// Grab my own PID
pid = Integer.toString(ProcessTools.getProcessId());