comparison doc/testing.html @ 54576:aa626cbadf1b

8222550: runtime/MemberName/MemberNameLeak.java times out Reviewed-by: coleenp, dholmes
author stefank
date Wed, 17 Apr 2019 07:41:12 +0200
parents 5ae4d3f46537
children b95ebdbf68ca
comparison
equal deleted inserted replaced
15:6c5ca3b04988 16:6588a1dd7872
39 <li><a href="#gtest-keywords">Gtest keywords</a></li> 39 <li><a href="#gtest-keywords">Gtest keywords</a></li>
40 <li><a href="#microbenchmark-keywords">Microbenchmark keywords</a></li> 40 <li><a href="#microbenchmark-keywords">Microbenchmark keywords</a></li>
41 </ul></li> 41 </ul></li>
42 <li><a href="#notes-for-specific-tests">Notes for Specific Tests</a><ul> 42 <li><a href="#notes-for-specific-tests">Notes for Specific Tests</a><ul>
43 <li><a href="#docker-tests">Docker Tests</a></li> 43 <li><a href="#docker-tests">Docker Tests</a></li>
44 <li><a href="#non-us-locale">Non-US locale</a></li>
44 </ul></li> 45 </ul></li>
45 </ul> 46 </ul>
46 </nav> 47 </nav>
47 <h2 id="using-make-test-the-run-test-framework">Using &quot;make test&quot; (the run-test framework)</h2> 48 <h2 id="using-make-test-the-run-test-framework">Using &quot;make test&quot; (the run-test framework)</h2>
48 <p>This new way of running tests is developer-centric. It assumes that you have built a JDK locally and want to test it. Running common test targets is simple, and more complex ad-hoc combination of tests is possible. The user interface is forgiving, and clearly report errors it cannot resolve.</p> 49 <p>This new way of running tests is developer-centric. It assumes that you have built a JDK locally and want to test it. Running common test targets is simple, and more complex ad-hoc combination of tests is possible. The user interface is forgiving, and clearly report errors it cannot resolve.</p>
192 <h3 id="docker-tests">Docker Tests</h3> 193 <h3 id="docker-tests">Docker Tests</h3>
193 <p>Docker tests with default parameters may fail on systems with glibc versions not compatible with the one used in the default docker image (e.g., Oracle Linux 7.6 for x86). For example, they pass on Ubuntu 16.04 but fail on Ubuntu 18.04 if run like this on x86:</p> 194 <p>Docker tests with default parameters may fail on systems with glibc versions not compatible with the one used in the default docker image (e.g., Oracle Linux 7.6 for x86). For example, they pass on Ubuntu 16.04 but fail on Ubuntu 18.04 if run like this on x86:</p>
194 <pre><code>$ make test TEST=&quot;jtreg:test/hotspot/jtreg/containers/docker&quot;</code></pre> 195 <pre><code>$ make test TEST=&quot;jtreg:test/hotspot/jtreg/containers/docker&quot;</code></pre>
195 <p>To run these tests correctly, additional parameters for the correct docker image are required on Ubuntu 18.04 by using <code>JAVA_OPTIONS</code>.</p> 196 <p>To run these tests correctly, additional parameters for the correct docker image are required on Ubuntu 18.04 by using <code>JAVA_OPTIONS</code>.</p>
196 <pre><code>$ make test TEST=&quot;jtreg:test/hotspot/jtreg/containers/docker&quot; JTREG=&quot;JAVA_OPTIONS=-Djdk.test.docker.image.name=ubuntu -Djdk.test.docker.image.version=latest&quot;</code></pre> 197 <pre><code>$ make test TEST=&quot;jtreg:test/hotspot/jtreg/containers/docker&quot; JTREG=&quot;JAVA_OPTIONS=-Djdk.test.docker.image.name=ubuntu -Djdk.test.docker.image.version=latest&quot;</code></pre>
198 <h3 id="non-us-locale">Non-US locale</h3>
199 <p>If your locale is non-US, some tests are likely to fail. To work around this you can set the locale to US. On Unix platforms simply setting <code>LANG=&quot;en_US&quot;</code> in the environment before running tests should work. On Windows, setting <code>JTREG=&quot;VM_OPTIONS=-Duser.language=en -Duser.country=US&quot;</code> helps for most, but not all test cases. For example:</p>
200 <pre><code>$ export LANG=&quot;en_US&quot; &amp;&amp; make test TEST=...
201 $ make test JTREG=&quot;VM_OPTIONS=-Duser.language=en -Duser.country=US&quot; TEST=...</code></pre>
197 </body> 202 </body>
198 </html> 203 </html>