JDK-8222120 : Clean up exit codes in tests
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.lang:reflect
  • Affected Version: 13
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2019-04-08
  • Updated: 2021-10-22
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.
Other
tbdUnresolved
Related Reports
Relates :  
JDK-8222111 - exeCallerAccessTest.c fails to build: control reaches end of non-void function
Description
After JDK-8222111 is fixed, there are two follow-ups:
 
First, the exit code should be communicated with "return $code;" rather than "exit($code)" in some tests. For example:
 test/jdk/java/lang/reflect/exeCallerAccessTest/exeCallerAccessTest.c
 test/jdk/tools/launcher/exeJniInvocationTest.c

Second, the returns from "int main(...)" should always be present, for example in:
  test/jdk/tools/launcher/exeJniInvocationTest.c
Comments
Please evaluate and reassign if appropriate.
11-04-2019