433 the diff between the specified revision and the repository tip.</p>
434 <p>The report is stored in
435 <code>build/$BUILD/test-results/jcov-output/diff_coverage_report</code>
436 file.</p>
437 <h4 id="aot_jdk">AOT_JDK</h4>
438 <p>See <a href="#testing-ahead-of-time-optimizations">Testing
439 Ahead-of-time optimizations</a>.</p>
440 <h3 id="jtreg-keywords">JTReg keywords</h3>
441 <h4 id="jobs-1">JOBS</h4>
442 <p>The test concurrency (<code>-concurrency</code>).</p>
443 <p>Defaults to TEST_JOBS (if set by <code>--with-test-jobs=</code>),
444 otherwise it defaults to JOBS, except for Hotspot, where the default is
445 <em>number of CPU cores/2</em>, but never more than <em>memory size in
446 GB/2</em>.</p>
447 <h4 id="timeout_factor-1">TIMEOUT_FACTOR</h4>
448 <p>The <code>TIMEOUT_FACTOR</code> is forwarded to JTReg framework
449 itself (<code>-timeoutFactor</code>). Also, some test cases that
450 programmatically wait a certain amount of time will apply this factor.
451 If we run in forced compilation mode (<code>-Xcomp</code>), the build
452 system will automatically adjust this factor to compensate for less
453 performance. Defaults to 1.</p>
454 <h4 id="failure_handler_timeout">FAILURE_HANDLER_TIMEOUT</h4>
455 <p>Sets the argument <code>-timeoutHandlerTimeout</code> for JTReg. The
456 default value is 0. This is only valid if the failure handler is
457 built.</p>
458 <h4 id="test_thread_factory">TEST_THREAD_FACTORY</h4>
459 <p>Sets the <code>-testThreadFactory</code> for JTReg. It should be the
460 fully qualified classname of a class which implements
461 <code>java.util.concurrent.ThreadFactory</code>. One such implementation
462 class, named Virtual, is currently part of the JDK build in the
463 <code>test/jtreg_test_thread_factory/</code> directory. This class gets
464 compiled during the test image build. The implementation of the Virtual
465 class creates a new virtual thread for executing each test class.</p>
466 <h4 id="jvmti_stress_agent">JVMTI_STRESS_AGENT</h4>
467 <p>Executes JTReg tests with JVM TI stress agent. The stress agent is
468 the part of test library and located in
469 <code>test/lib/jdk/test/lib/jvmti/libJvmtiStressAgent.cpp</code>. The
470 value of this argument is set as JVM TI agent options. This mode uses
471 ProblemList-jvmti-stress-agent.txt as an additional exclude list.</p>
472 <h4 id="test_mode">TEST_MODE</h4>
473 <p>The test mode (<code>agentvm</code> or <code>othervm</code>).</p>

433 the diff between the specified revision and the repository tip.</p>
434 <p>The report is stored in
435 <code>build/$BUILD/test-results/jcov-output/diff_coverage_report</code>
436 file.</p>
437 <h4 id="aot_jdk">AOT_JDK</h4>
438 <p>See <a href="#testing-ahead-of-time-optimizations">Testing
439 Ahead-of-time optimizations</a>.</p>
440 <h3 id="jtreg-keywords">JTReg keywords</h3>
441 <h4 id="jobs-1">JOBS</h4>
442 <p>The test concurrency (<code>-concurrency</code>).</p>
443 <p>Defaults to TEST_JOBS (if set by <code>--with-test-jobs=</code>),
444 otherwise it defaults to JOBS, except for Hotspot, where the default is
445 <em>number of CPU cores/2</em>, but never more than <em>memory size in
446 GB/2</em>.</p>
447 <h4 id="timeout_factor-1">TIMEOUT_FACTOR</h4>
448 <p>The <code>TIMEOUT_FACTOR</code> is forwarded to JTReg framework
449 itself (<code>-timeoutFactor</code>). Also, some test cases that
450 programmatically wait a certain amount of time will apply this factor.
451 If we run in forced compilation mode (<code>-Xcomp</code>), the build
452 system will automatically adjust this factor to compensate for less
453 performance. Defaults to 4.</p>
454 <h4 id="failure_handler_timeout">FAILURE_HANDLER_TIMEOUT</h4>
455 <p>Sets the argument <code>-timeoutHandlerTimeout</code> for JTReg. The
456 default value is 0. This is only valid if the failure handler is
457 built.</p>
458 <h4 id="test_thread_factory">TEST_THREAD_FACTORY</h4>
459 <p>Sets the <code>-testThreadFactory</code> for JTReg. It should be the
460 fully qualified classname of a class which implements
461 <code>java.util.concurrent.ThreadFactory</code>. One such implementation
462 class, named Virtual, is currently part of the JDK build in the
463 <code>test/jtreg_test_thread_factory/</code> directory. This class gets
464 compiled during the test image build. The implementation of the Virtual
465 class creates a new virtual thread for executing each test class.</p>
466 <h4 id="jvmti_stress_agent">JVMTI_STRESS_AGENT</h4>
467 <p>Executes JTReg tests with JVM TI stress agent. The stress agent is
468 the part of test library and located in
469 <code>test/lib/jdk/test/lib/jvmti/libJvmtiStressAgent.cpp</code>. The
470 value of this argument is set as JVM TI agent options. This mode uses
471 ProblemList-jvmti-stress-agent.txt as an additional exclude list.</p>
472 <h4 id="test_mode">TEST_MODE</h4>
473 <p>The test mode (<code>agentvm</code> or <code>othervm</code>).</p>