P3
The only docs that come with jtreg for -concurrency are:
-conc:<factor> | -concurrency:<factor>
concurrency factor
-conc:auto is undocumented, e.g. "jtreg -onlineHelp auto" comes up empty.
(It's another matter that -conc:auto is becoming more dangerous as the number of cpus per machine increases exponentially; I also see -conc:auto failing because of jtharness 50 cpu limit)
But there's the excellent page
http://openjdk.java.net/jtreg/concurrency.html
that's easy to miss.
The fact that there's 3 sources of docs, jtreg -help, jtreg -onlineHelp and the website is a maintenance problem.
I read
"""Note: tests that can use or need to use a significant proportion of a system resources should be declared as "exclusiveAccess" tests, so that jtreg avoid running other tests at the same time."""
which suggests that exclusiveAccess is about system resources, but then I also read
"""exclusiveAccess.dirs <directories>
Directories containing tests which should not be run concurrently at the same time as other tests. A harness that supports concurrent test execution should ensure that all tests in the specified directories are run when no other tests in the same directory is being run."""
Is it really "other tests in the same directory"? That would imply this option is only about mutual interference. Does putting every such test in a directory by itself accomplish nothing? Probably we should delete "in the same directory"? Then, why is exclusiveAccess a per-directory option? I would like to apply it to individual resource-intensive multi-threaded tests.
-conc:<factor> | -concurrency:<factor>
concurrency factor
-conc:auto is undocumented, e.g. "jtreg -onlineHelp auto" comes up empty.
(It's another matter that -conc:auto is becoming more dangerous as the number of cpus per machine increases exponentially; I also see -conc:auto failing because of jtharness 50 cpu limit)
But there's the excellent page
http://openjdk.java.net/jtreg/concurrency.html
that's easy to miss.
The fact that there's 3 sources of docs, jtreg -help, jtreg -onlineHelp and the website is a maintenance problem.
I read
"""Note: tests that can use or need to use a significant proportion of a system resources should be declared as "exclusiveAccess" tests, so that jtreg avoid running other tests at the same time."""
which suggests that exclusiveAccess is about system resources, but then I also read
"""exclusiveAccess.dirs <directories>
Directories containing tests which should not be run concurrently at the same time as other tests. A harness that supports concurrent test execution should ensure that all tests in the specified directories are run when no other tests in the same directory is being run."""
Is it really "other tests in the same directory"? That would imply this option is only about mutual interference. Does putting every such test in a directory by itself accomplish nothing? Probably we should delete "in the same directory"? Then, why is exclusiveAccess a per-directory option? I would like to apply it to individual resource-intensive multi-threaded tests.