JDK-8073159 : improve Test6857159.java
- Type: Bug
- Component: hotspot
- Sub-Component: compiler
- Affected Version: 9
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2015-02-13
- Updated: 2019-03-19
- Resolved: 2016-05-31
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.
To download the current JDK release, click here.
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.
To download the current JDK release, click here.
| JDK 8 | JDK 9 |
|---|---|
8u202Fixed  |
9 b126Fixed |
Related Reports
|
Relates :
|
Description
fix for 8068440 missed an exit code check and passing external vm flags to spawn jvm. On 02/04/2015 06:26 PM, Igor Ignatyev wrote: > On 02/02/2015 10:55 AM, Albert Noll wrote: >> Hi Igor, >> >> thanks for you response. >> On 01/29/2015 06:38 PM, Igor Ignatyev wrote: >>> I meant to check that exit code of spawn java process is zero. >>> >> Can I find that somewhere in the log files? > you can check it by OutputAnalyzer::shouldHaveExitValue(0) >>> also I missed that you use ProcessTools.createJavaProcessBuilder >>> instead of ProcessTools.executeTestJvm to spawn tested jvm. so created >>> jvm ignores external vm flags. >>> >> Is this ok? > nope, you should use ProcessTools::executeTestJvm, otherwise we'll > unnoticeably lose coverage.
Comments
|