I wish to run a test exactly as jtreg runs it, in precisely the same environment and with the same options, so that I may debug it directly, and not after it has failed. My naive attempts at doing this produce different failures of the form:
Exception in thread "main" java.lang.SecurityException: Prohibited package name: java.util.Random
because the test has the name java.util.Random.RandomStreamTest. Perhaps that was a poor choice of test name. I am sure that given sufficient time I could determine a workaround for this, but wouldn't it be nice if I did not need to do this.
Jtreg may already provide this information, but if it does, its location is not documented, at least not here: http://openjdk.java.net/jtreg/command-help.html (I have previously noticed that jtreg has multiple sometimes-inconsistent copies of its documentation) I also sampled many files with likely names in the JT* subdirectories, but did not find the information I was looking for.
One likely workaround is to rename the test into a different package to avoid the need to recreate whatever steps jtreg uses to dodge the package name error. This, of course, also takes time and also perturbs the test.
Exception in thread "main" java.lang.SecurityException: Prohibited package name: java.util.Random
because the test has the name java.util.Random.RandomStreamTest. Perhaps that was a poor choice of test name. I am sure that given sufficient time I could determine a workaround for this, but wouldn't it be nice if I did not need to do this.
Jtreg may already provide this information, but if it does, its location is not documented, at least not here: http://openjdk.java.net/jtreg/command-help.html (I have previously noticed that jtreg has multiple sometimes-inconsistent copies of its documentation) I also sampled many files with likely names in the JT* subdirectories, but did not find the information I was looking for.
One likely workaround is to rename the test into a different package to avoid the need to recreate whatever steps jtreg uses to dodge the package name error. This, of course, also takes time and also perturbs the test.
- duplicates
-
CODETOOLS-7900188 jtreg: -vmoptions missing from the log
-
- Closed
-
-
CODETOOLS-7900167 Make jtreg jtr files have exact java command lines so java command be rerun
-
- Closed
-
- relates to
-
CODETOOLS-7903024 Improve docs and impl for jtreg -show option
-
- Resolved
-