RFR: 8212008: Use of TREAT_EXIT_CODE_1_AS_0 hide problems with jtreg Java (original) (raw)
Christian Tornqvist christian.tornqvist at oracle.com
Wed Oct 10 15:47:50 UTC 2018
- Previous message (by thread): RFR: 8212004: Optional compile_commands.json field not compatible with older libclang
- Next message (by thread): RFR: 8212008: Use of TREAT_EXIT_CODE_1_AS_0 hide problems with jtreg Java
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi,
When running JDK and Hotspot jtreg tests through make, TREAT_EXIT_CODE_1_AS_0 is set to true. Any issue with the Java installation used to run jtreg won’t be reflected in the exit code. This has been seen a bunch of times in our internal CI system where we thought we ran tests but instead no tests were run at all because the jtreg Java installation had been deleted/corrupted.
Webrev: http://cr.openjdk.java.net/~ctornqvi/webrev/8212008/webrev.00/ <http://cr.openjdk.java.net/~ctornqvi/webrev/8212008/webrev.00/> Bug: https://bugs.openjdk.java.net/browse/JDK-8212008 <https://bugs.openjdk.java.net/browse/JDK-8212008>
Thanks, Christian
- Previous message (by thread): RFR: 8212004: Optional compile_commands.json field not compatible with older libclang
- Next message (by thread): RFR: 8212008: Use of TREAT_EXIT_CODE_1_AS_0 hide problems with jtreg Java
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]