19 * Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA
20 * or visit www.oracle.com if you need additional information or have any
21 * questions.
22 */
23 package jdk.test.lib.cds;
24
25 import java.io.IOException;
26 import java.io.File;
27 import java.io.FileOutputStream;
28 import java.io.PrintStream;
29 import java.text.SimpleDateFormat;
30 import java.util.ArrayList;
31 import java.util.Date;
32 import jdk.test.lib.Utils;
33 import jdk.test.lib.process.OutputAnalyzer;
34 import jdk.test.lib.process.ProcessTools;
35
36
37 // This class contains common test utilities for testing CDS
38 public class CDSTestUtils {
39 public interface Checker {
40 public void check(OutputAnalyzer output) throws Exception;
41 }
42
43 /*
44 * INTRODUCTION
45 *
46 * When testing various CDS functionalities, we need to launch JVM processes
47 * using a "launch method" (such as TestCommon.run), and analyze the results of these
48 * processes.
49 *
50 * While typical jtreg tests would use OutputAnalyzer in such cases, due to the
51 * complexity of CDS failure modes, we have added the CDSTestUtils.Result class
52 * to make the analysis more convenient and less error prone.
53 *
54 * A Java process can end in one of the following 4 states:
55 *
56 * 1: Unexpected error - such as JVM crashing. In this case, the "launch method"
57 * will throw a RuntimeException.
58 * 2: Mapping Failure - this happens when the OS (intermittently) fails to map the
|
19 * Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA
20 * or visit www.oracle.com if you need additional information or have any
21 * questions.
22 */
23 package jdk.test.lib.cds;
24
25 import java.io.IOException;
26 import java.io.File;
27 import java.io.FileOutputStream;
28 import java.io.PrintStream;
29 import java.text.SimpleDateFormat;
30 import java.util.ArrayList;
31 import java.util.Date;
32 import jdk.test.lib.Utils;
33 import jdk.test.lib.process.OutputAnalyzer;
34 import jdk.test.lib.process.ProcessTools;
35
36
37 // This class contains common test utilities for testing CDS
38 public class CDSTestUtils {
39 public static final String MSG_RANGE_NOT_WITHIN_HEAP =
40 "UseSharedSpaces: Unable to allocate region, range is not within java heap.";
41 public static final String MSG_RANGE_ALREADT_IN_USE =
42 "Unable to allocate region, java heap range is already in use.";
43
44 public interface Checker {
45 public void check(OutputAnalyzer output) throws Exception;
46 }
47
48 /*
49 * INTRODUCTION
50 *
51 * When testing various CDS functionalities, we need to launch JVM processes
52 * using a "launch method" (such as TestCommon.run), and analyze the results of these
53 * processes.
54 *
55 * While typical jtreg tests would use OutputAnalyzer in such cases, due to the
56 * complexity of CDS failure modes, we have added the CDSTestUtils.Result class
57 * to make the analysis more convenient and less error prone.
58 *
59 * A Java process can end in one of the following 4 states:
60 *
61 * 1: Unexpected error - such as JVM crashing. In this case, the "launch method"
62 * will throw a RuntimeException.
63 * 2: Mapping Failure - this happens when the OS (intermittently) fails to map the
|