-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Closes #10611 - Fix exit status of Flank #10612
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure this will work. The reason why we use a function to set the exit code is that we still want some artifacts to be written regardless of pass or fail outcome. Most of the terminate on fail bash functions will end the script abruptly. I think we still need to capture the return code from the Java execution in a variable and hold onto it til the end. Not sure if pipefail is doing that
Setting pipefail will get us the the exit code of the process that's piped to another (sets the exit status $? to the exit code of the last program to exit non-zero (or zero if all exited successfully)). E.g, what's happening now $ false | true; echo $?
0 and after (see the ui-test-x86 debug failed above showing the right result now) $ set -o pipefail
$ false | true; echo $?
1 |
per our zoom sesion LGTM 👍 |
9b47ed8
to
34cd540
Compare
Codecov Report
@@ Coverage Diff @@
## master #10612 +/- ##
============================================
+ Coverage 19.20% 19.40% +0.20%
- Complexity 599 602 +3
============================================
Files 360 359 -1
Lines 14801 14638 -163
Branches 2001 1967 -34
============================================
- Hits 2842 2841 -1
+ Misses 11699 11537 -162
Partials 260 260
Continue to review full report at Codecov.
|
34cd540
to
48ce80d
Compare
48ce80d
to
4b72a89
Compare
Closes #10611