371 Additional VM arguments to provide to forked off VMs. Same as `-jvmArgs <args>`
 372 
 373 #### OPTIONS
 374 Additional arguments to send to JMH.
 375 
 376 ## Notes for Specific Tests
 377 
 378 ### Docker Tests
 379 
 380 Docker tests with default parameters may fail on systems with glibc versions not
 381 compatible with the one used in the default docker image (e.g., Oracle Linux 7.6 for x86).
 382 For example, they pass on Ubuntu 16.04 but fail on Ubuntu 18.04 if run like this on x86:
 383 
 384     $ make test TEST="jtreg:test/hotspot/jtreg/containers/docker"
 385 
 386 To run these tests correctly, additional parameters for the correct docker image are
 387 required on Ubuntu 18.04 by using `JAVA_OPTIONS`.
 388 
 389     $ make test TEST="jtreg:test/hotspot/jtreg/containers/docker" JTREG="JAVA_OPTIONS=-Djdk.test.docker.image.name=ubuntu -Djdk.test.docker.image.version=latest"
 390 











 391 ---
 392 # Override some definitions in the global css file that are not optimal for
 393 # this document.
 394 header-includes:
 395  - '<style type="text/css">pre, code, tt { color: #1d6ae5; }</style>'
 396 ---

 371 Additional VM arguments to provide to forked off VMs. Same as `-jvmArgs <args>`
 372 
 373 #### OPTIONS
 374 Additional arguments to send to JMH.
 375 
 376 ## Notes for Specific Tests
 377 
 378 ### Docker Tests
 379 
 380 Docker tests with default parameters may fail on systems with glibc versions not
 381 compatible with the one used in the default docker image (e.g., Oracle Linux 7.6 for x86).
 382 For example, they pass on Ubuntu 16.04 but fail on Ubuntu 18.04 if run like this on x86:
 383 
 384     $ make test TEST="jtreg:test/hotspot/jtreg/containers/docker"
 385 
 386 To run these tests correctly, additional parameters for the correct docker image are
 387 required on Ubuntu 18.04 by using `JAVA_OPTIONS`.
 388 
 389     $ make test TEST="jtreg:test/hotspot/jtreg/containers/docker" JTREG="JAVA_OPTIONS=-Djdk.test.docker.image.name=ubuntu -Djdk.test.docker.image.version=latest"
 390 
 391 ### Non-US locale
 392 
 393 If your locale is non-US, some tests are likely to fail. To work around this you can
 394 set the locale to US. On Unix platforms simply setting `LANG="en_US"` in the
 395 environment before running tests should work. On Windows, setting
 396 `JTREG="VM_OPTIONS=-Duser.language=en -Duser.country=US"` helps for most, but not all test cases.
 397 For example:
 398 
 399     $export LANG="en_US" && make test TEST=...
 400     $make test JTREG="VM_OPTIONS=-Duser.language=en -Duser.country=US" TEST=...
 401 
 402 ---
 403 # Override some definitions in the global css file that are not optimal for
 404 # this document.
 405 header-includes:
 406  - '<style type="text/css">pre, code, tt { color: #1d6ae5; }</style>'
 407 ---