-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Return code successful on task failure #35
Comments
OK, apparently this goes deeper. If I drop the task again and retry I get this:
But again, the status code indicates success ... |
And one more finding: the return code apparently works fine for the implicit Given this task_default() {
false
} The behavior is as expected:
However, explicitly invoking that task shows the wrong behavior again:
|
After a little debugging I found that - runner_run_task "${task}" || return
+ runner_run_task "${task}" || return $? Could it be that a plain |
I had that issue with plain returns, and i thought most of them were fixed. It is supposed to implicitly return the last exit code, but with such bugs popping up I am no longer sure. Good catch. |
@stylemistake Any updates on this? We had to gradually drop the Task Runner in all of our builds due to this ... |
@mbrodala I have pushed a fix, along with a test for your case. Check if it works for you, and if you need a new release on npm, let me know. P.S. You could've submitted a pull request for that kind of thing. I'm a pretty chill guy at accepting PRs. :) |
I wasn't 100% sure that my fix was the fix but evidently it works now, thanks. :-) |
Given the following
Runnerfile.sh
:When running this task I see this output:
The overall return code indicates success, any idea what's wrong here? Could this be related to #32?
The text was updated successfully, but these errors were encountered: