GitHub user vanzin opened a pull request:

    https://github.com/apache/spark/pull/12910

    [SPARK-13670][launcher] Propagate error from launcher to shell.

    bash doesn't really propagate errors from subshells when using redirection
    the way spark-class does; so, instead, this change captures the exit code
    of the launcher process in the command array, and checks it before executing
    the actual command.
    
    Tested by injecting an error in Main.java (the launcher entry point) and
    verifying the shell gets the right exit code from spark-class.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/vanzin/spark SPARK-13670

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/12910.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #12910
    
----
commit 552a48f09d627c6739e2c802a2821417be981c6f
Author: Marcelo Vanzin <[email protected]>
Date:   2016-05-04T21:40:46Z

    [SPARK-13670][launcher] Propagate error from launcher to shell.
    
    bash doesn't really propagate errors from subshells when using redirection
    the way spark-class does; so, instead, this change captures the exit code
    of the launcher process in the command array, and checks it before executing
    the actual command.
    
    Tested by injecting an error in Main.java (the launcher entry point) and
    verifying the shell gets the right exit code from spark-class.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to