There are a lot of stress tests in the different hotspot areas. Usually they take more time to execute then standard tests.

There is a request to simplify non-stress test execution for developers. So testing like
make run-test TEST=...
can be simply adopted to don't run stress tests.

The potential ideas:
1) use keyword 'stress' to mark stress tests and simplify way to skip non-stress tests
    make run-test STRESS_TESTS=disable/enable/only TEST=...
2) use keyword 'stress' and don't run stress tests by default
   might be not that some developers expect, and there would be question about how to run stress tests/all tests
3) separate the stress tests from "standard" tests
./test/hotspot/jtreg/stress/<component>-common

The 3) allows to clearly separate stress tests in the layout and easily share stress test codes. It is not required for sanity testing, I think. While it is not possible to easy share test code between standard and stress tests.
 


The list of stress directory:
./test/jdk/java/lang/Thread/virtual/stress
./test/hotspot/jtreg/gc/stress
./test/hotspot/jtreg/compiler/arraycopy/stress
./test/hotspot/jtreg/compiler/codecache/stress
./test/hotspot/jtreg/serviceability/jvmti/stress

and a lot of stress tests in VmTestbase, which are not needed to be processed right now.

./test/hotspot/jtreg/vmTestbase/vm/mlvm/mixed/stress
.//test/hotspot/jtreg/vmTestbase/vm/mlvm/meth/stress
./test/hotspot/jtreg/vmTestbase/vm/mlvm/hiddenloader/stress
./test/hotspot/jtreg/vmTestbase/vm/mlvm/cp/stress
./test/hotspot/jtreg/vmTestbase/vm/mlvm/indy/stress
./test/hotspot/jtreg/vmTestbase/nsk/sysdict/vm/stress
./test/hotspot/jtreg/vmTestbase/nsk/jdi/stress
./test/hotspot/jtreg/vmTestbase/nsk/monitoring/stress
./test/hotspot/jtreg/vmTestbase/nsk/stress