21 |
21 |
22 $ make test-tier1 |
22 $ make test-tier1 |
23 $ make test-jdk_lang JTREG="JOBS=8" |
23 $ make test-jdk_lang JTREG="JOBS=8" |
24 $ make test TEST=jdk_lang |
24 $ make test TEST=jdk_lang |
25 $ make test-only TEST="gtest:LogTagSet gtest:LogTagSetDescriptions" GTEST="REPEAT=-1" |
25 $ make test-only TEST="gtest:LogTagSet gtest:LogTagSetDescriptions" GTEST="REPEAT=-1" |
26 $ make test TEST="hotspot:hotspot_gc" JTREG="JOBS=1;TIMEOUT=8;VM_OPTIONS=-XshowSettings -Xlog:gc+ref=debug" |
26 $ make test TEST="hotspot:hotspot_gc" JTREG="JOBS=1;TIMEOUT_FACTOR=8;VM_OPTIONS=-XshowSettings -Xlog:gc+ref=debug" |
27 $ make test TEST="jtreg:test/hotspot:hotspot_gc test/hotspot/jtreg/native_sanity/JniVersion.java" |
27 $ make test TEST="jtreg:test/hotspot:hotspot_gc test/hotspot/jtreg/native_sanity/JniVersion.java" |
28 $ make test TEST="micro:java.lang.reflect" MICRO="FORK=1;WARMUP_ITER=2" |
28 $ make test TEST="micro:java.lang.reflect" MICRO="FORK=1;WARMUP_ITER=2" |
29 $ make exploded-test TEST=tier2 |
29 $ make exploded-test TEST=tier2 |
30 |
30 |
31 ### Configuration |
31 ### Configuration |
178 |
178 |
179 It is possible to control various aspects of the test suites using make control |
179 It is possible to control various aspects of the test suites using make control |
180 variables. |
180 variables. |
181 |
181 |
182 These variables use a keyword=value approach to allow multiple values to be |
182 These variables use a keyword=value approach to allow multiple values to be |
183 set. So, for instance, `JTREG="JOBS=1;TIMEOUT=8"` will set the JTReg |
183 set. So, for instance, `JTREG="JOBS=1;TIMEOUT_FACTOR=8"` will set the JTReg |
184 concurrency level to 1 and the timeout factor to 8. This is equivalent to |
184 concurrency level to 1 and the timeout factor to 8. This is equivalent to |
185 setting `JTREG_JOBS=1 JTREG_TIMEOUT=8`, but using the keyword format means that |
185 setting `JTREG_JOBS=1 JTREG_TIMEOUT_FACTOR=8`, but using the keyword format means that |
186 the `JTREG` variable is parsed and verified for correctness, so |
186 the `JTREG` variable is parsed and verified for correctness, so |
187 `JTREG="TMIEOUT=8"` would give an error, while `JTREG_TMIEOUT=8` would just |
187 `JTREG="TMIEOUT_FACTOR=8"` would give an error, while `JTREG_TMIEOUT_FACTOR=8` would just |
188 pass unnoticed. |
188 pass unnoticed. |
189 |
189 |
190 To separate multiple keyword=value pairs, use `;` (semicolon). Since the shell |
190 To separate multiple keyword=value pairs, use `;` (semicolon). Since the shell |
191 normally eats `;`, the recommended usage is to write the assignment inside |
191 normally eats `;`, the recommended usage is to write the assignment inside |
192 qoutes, e.g. `JTREG="...;..."`. This will also make sure spaces are preserved, |
192 qoutes, e.g. `JTREG="...;..."`. This will also make sure spaces are preserved, |
193 as in `JTREG="VM_OPTIONS=-XshowSettings -Xlog:gc+ref=debug"`. |
193 as in `JTREG="VM_OPTIONS=-XshowSettings -Xlog:gc+ref=debug"`. |
194 |
194 |
195 (Other ways are possible, e.g. using backslash: `JTREG=JOBS=1\;TIMEOUT=8`. |
195 (Other ways are possible, e.g. using backslash: `JTREG=JOBS=1\;TIMEOUT_FACTOR=8`. |
196 Also, as a special technique, the string `%20` will be replaced with space for |
196 Also, as a special technique, the string `%20` will be replaced with space for |
197 certain options, e.g. `JTREG=VM_OPTIONS=-XshowSettings%20-Xlog:gc+ref=debug`. |
197 certain options, e.g. `JTREG=VM_OPTIONS=-XshowSettings%20-Xlog:gc+ref=debug`. |
198 This can be useful if you have layers of scripts and have trouble getting |
198 This can be useful if you have layers of scripts and have trouble getting |
199 proper quoting of command line arguments through.) |
199 proper quoting of command line arguments through.) |
200 |
200 |