The test specifications given in TEST is parsed into fully qualified testĭescriptors, which clearly and unambigously show which tests will be run. Test runs, the run-test TEST='x' solution needs to be used. This means that make run-test-tier1 is equivalent to make run-test TEST='tier1', but the latter is more tab-completion friendly. Includes all JTReg test groups, the hotspot gtest, and custom tests (if To speed up subsequent test runs with no source code changes, run-test-only canīe used instead, which do not depend on the source and test image build.įor some common top-level tests, direct make targets have been generated. In this useĬase, the test or tests to be executed is controlled using the TEST variable. (An alternative is to set the JT_HOMEĮnvironment variable to point to the JTReg home before running configure.) Test selectionĪll functionality is available using the run-test make target. the top directory,Ĭontaining lib/jtreg.jar etc.

Note that this option should point to the JTReg home, i.e. The -with-jtreg= option to point to the JTReg framework.

If it is not picked up automatically by configure, use To be able to run JTReg tests, configure needs to know where to find the $ make run-test TEST='jtreg:test/hotspot:hotspot_gc test/hotspot/jtreg/native_sanity/JniVersion.java' $ make run-test TEST='hotspot:hotspot_gc' JTREG='JOBS=1 TIMEOUT=8 VM_OPTIONS=-XshowSettings -Xlog:gc+ref=debug' $ make run-test-only TEST='gtest:LogTagSet gtest:LogTagSetDescriptions' GTEST='REPEAT=-1'

Openjdk 8 windows