The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed. Resolved: Release in which this issue/RFE has been resolved. Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
Once use of jtreg 4.1 has become the default and widely adopted, we should update any langtools/ and jdk/ shell tests to use $COMPILEJAVA/bin/javac instead of $TESTJAVA/bin/javac as needed.
Comments
In general, I think we've progressed to the point where we're often calling javac via API, which gets into a different evolutionary discussion of using @run driver, and the recent ideas for /stable and /test options for action tags.
27-10-2017
It doesn't look like there's anything left to fix up here. This is a couple years old, so it's likely that most tests have already been updated to work with the latest jtreg. Closing as Cannot Reproduce.
27-10-2017
#section:shell
----------messages:(3/116)----------
command: shell InheritIO.sh
reason: User specified action: run shell InheritIO.sh
elapsed time (seconds): 1.738
----------System.out:(3/205)----------
FAIL: unexpected ' 4 [main] printf 6048 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list cygwin@cygwin.com
exit value: 0' in stderr
----------System.err:(2/158)----------
3 [main] sh 12088 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list cygwin@cygwin.com
test result: Failed. Execution failed: exit code 1
11-03-2014
Yes, you are right... Not sure why they were run on runtime...
13-11-2013
Roman - I don't understand the last few comments that you have added to this bug. Are you testing a JDK or a runtime (runtime meaning the JRE or one of the Compact Profile builds). I ask because the tests that are listed in recent comments are use tools and aren't really applicable when testing a runtime. I believe David Holmes has the TEST.groups configured so that tests that test tools are only run when testing a JDK. When testing a runtime then you need of course to specify a compile JDK to be used by tests that need to use tools.
13-11-2013
The same for HotSpot:
http://aurora.ru.oracle.com/functional/faces/RunDetails.xhtml?names=301983.JAVASE_EMBEDDED_PROMOTION_TESTCYCLE_8_ALL-2748
RULE runtime/7194254/Test7194254.java Exception java.io.IOException: Cannot run program "...": error=2, No such file or directory
18-10-2013
It would be good to get this bug updated with the current list of tests that need to be fixed. The closed logging tests for example are relatively new and seem to be have been added after we did the big update to use COMPILEJAVA.
17-10-2013
Removed "test-fail-mod" label to turn on matching in Aurora
17-10-2013
Alan, evaluation of b110 is in progress now. So this list will be after about a week.
17-10-2013
It would be good to check if there is anything more needed here, we may be able to close this bug.
13-08-2013
The tests listed in this issue have already been updated to use $COMPILEJAVA. We can probably close this one as a dup of JDK-8005978.
29-05-2013
EVALUATION
We could proactively anticipate jtreg 4.1 by changing the tests to use COMPILEJAVA and then include a default assignment to set COMPILEJAVA to TESTJAVA is COMPILEJAVA is unset.