You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@spark.apache.org by felixcheung <gi...@git.apache.org> on 2016/04/22 23:58:44 UTC

[GitHub] spark pull request: [SPARK-14594][SPARKR] check execution return s...

GitHub user felixcheung opened a pull request:

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

    [SPARK-14594][SPARKR] check execution return status code

    ## What changes were proposed in this pull request?
    
    When JVM backend fails without going proper error handling (eg. process crashed), the R error message could be ambiguous.
    
    ```
    Error in if (returnStatus != 0) { : argument is of length zero
    ```
    
    This change attempts to make it more clear (however, one would still need to investigate why JVM fails)
    
    ## How was this patch tested?
    
    manually

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

    $ git pull https://github.com/felixcheung/spark rreturnstatus

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

    https://github.com/apache/spark/pull/12622.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 #12622
    
----
commit f5f46c56bccaf289ac670027406fc1d19cd41c9d
Author: felixcheung <fe...@hotmail.com>
Date:   2016-04-22T21:55:13Z

    check execution return status code

----


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


[GitHub] spark pull request: [SPARK-14594][SPARKR] check execution return s...

Posted by AmplabJenkins <gi...@git.apache.org>.
Github user AmplabJenkins commented on the pull request:

    https://github.com/apache/spark/pull/12622#issuecomment-213607112
  
    Merged build finished. Test PASSed.


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


[GitHub] spark pull request: [SPARK-14594][SPARKR] check execution return s...

Posted by shivaram <gi...@git.apache.org>.
Github user shivaram commented on the pull request:

    https://github.com/apache/spark/pull/12622#issuecomment-213637395
  
    LGTM.  It'll be good to know more information though. Maybe we can add a log message for the JVM with an exit handler or something like that ?


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


[GitHub] spark pull request: [SPARK-14594][SPARKR] check execution return s...

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

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


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


[GitHub] spark pull request: [SPARK-14594][SPARKR] check execution return s...

Posted by AmplabJenkins <gi...@git.apache.org>.
Github user AmplabJenkins commented on the pull request:

    https://github.com/apache/spark/pull/12622#issuecomment-213607114
  
    Test PASSed.
    Refer to this link for build results (access rights to CI server needed): 
    https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/56741/
    Test PASSed.


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


[GitHub] spark pull request: [SPARK-14594][SPARKR] check execution return s...

Posted by SparkQA <gi...@git.apache.org>.
Github user SparkQA commented on the pull request:

    https://github.com/apache/spark/pull/12622#issuecomment-213603334
  
    **[Test build #56741 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56741/consoleFull)** for PR 12622 at commit [`f5f46c5`](https://github.com/apache/spark/commit/f5f46c56bccaf289ac670027406fc1d19cd41c9d).


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


[GitHub] spark pull request: [SPARK-14594][SPARKR] check execution return s...

Posted by shivaram <gi...@git.apache.org>.
Github user shivaram commented on the pull request:

    https://github.com/apache/spark/pull/12622#issuecomment-213797832
  
    Ok - this is good for now. I'll merge this PR and we can revisit this if we have a better repro.


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


[GitHub] spark pull request: [SPARK-14594][SPARKR] check execution return s...

Posted by felixcheung <gi...@git.apache.org>.
Github user felixcheung commented on the pull request:

    https://github.com/apache/spark/pull/12622#issuecomment-213795814
  
    JVM addShutdownHook is being added for a couple for things and they have logging, for example:
    
    https://github.com/apache/spark/blob/master/core/src/main/scala/org/apache/spark/util/ShutdownHookManager.scala
    https://github.com/apache/spark/blob/af1f4da76268115c5a4cc3035d3236ad27f7240a/core/src/main/scala/org/apache/spark/SparkContext.scala#L559
    But unfortunately they are not guaranteed to be called if the process is terminated abruptly.
    If we are concerned I think we should get a specific repro step to check if we have logging for that case, if possible.
        
    
      


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


[GitHub] spark pull request: [SPARK-14594][SPARKR] check execution return s...

Posted by SparkQA <gi...@git.apache.org>.
Github user SparkQA commented on the pull request:

    https://github.com/apache/spark/pull/12622#issuecomment-213607049
  
    **[Test build #56741 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56741/consoleFull)** for PR 12622 at commit [`f5f46c5`](https://github.com/apache/spark/commit/f5f46c56bccaf289ac670027406fc1d19cd41c9d).
     * This patch passes all tests.
     * This patch merges cleanly.
     * This patch adds no public classes.


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org