[GitHub] spark pull request: [SPARK-10001][Core][Hotfix] Don't short-circui...
Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/12745#issuecomment-215302102 **[Test build #2898 has started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2898/consoleFull)** for PR 12745 at commit [`7fe0e54`](https://github.com/apache/spark/commit/7fe0e54c5e39ff942fd58a16d5e5e309887ee883). --- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org
[GitHub] spark pull request: [SPARK-10001][Core][Hotfix] Don't short-circui...
Github user rxin commented on a diff in the pull request: https://github.com/apache/spark/pull/12745#discussion_r61370370 --- Diff: core/src/main/scala/org/apache/spark/util/SignalUtils.scala --- @@ -94,7 +94,7 @@ private[spark] object SignalUtils extends Logging { // run all actions, escalate to parent handler if no action catches the signal // (i.e. all actions return false) - val escalate = actions.asScala.forall { action => !action() } + val escalate = actions.asScala.map(action => action()).forall(_ == false) --- End diff -- we should probably leave a comment here saying why we are doing map and then forall, to make sure nobody would come in and "optimize" the map.forall into just a forall. --- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org
[GitHub] spark pull request: [SPARK-10001][Core][Hotfix] Don't short-circui...
Github user rxin commented on the pull request: https://github.com/apache/spark/pull/12745#issuecomment-215301937 @jodersky this really isn't a hot fix. Can you remove that label? --- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org
[GitHub] spark pull request: [SPARK-10001][Core][Hotfix] Don't short-circui...
Github user jodersky commented on the pull request: https://github.com/apache/spark/pull/12745#issuecomment-215272244 looks like a flaky test jenkins, retest this please --- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org
[GitHub] spark pull request: [SPARK-10001][Core][Hotfix] Don't short-circui...
Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/12745#issuecomment-215271915 Merged build finished. Test FAILed. --- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org
[GitHub] spark pull request: [SPARK-10001][Core][Hotfix] Don't short-circui...
Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/12745#issuecomment-215271917 Test FAILed. Refer to this link for build results (access rights to CI server needed): https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/57188/ Test FAILed. --- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org
[GitHub] spark pull request: [SPARK-10001][Core][Hotfix] Don't short-circui...
Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/12745#issuecomment-215271778 **[Test build #57188 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/57188/consoleFull)** for PR 12745 at commit [`7fe0e54`](https://github.com/apache/spark/commit/7fe0e54c5e39ff942fd58a16d5e5e309887ee883). * This patch **fails Spark unit 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org
[GitHub] spark pull request: [SPARK-10001][Core][Hotfix] Don't short-circui...
Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/12745#issuecomment-215252572 **[Test build #57188 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/57188/consoleFull)** for PR 12745 at commit [`7fe0e54`](https://github.com/apache/spark/commit/7fe0e54c5e39ff942fd58a16d5e5e309887ee883). --- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org
[GitHub] spark pull request: [SPARK-10001][Core][Hotfix] Don't short-circui...
GitHub user jodersky opened a pull request: https://github.com/apache/spark/pull/12745 [SPARK-10001][Core][Hotfix] Don't short-circuit actions in signal handlers ## What changes were proposed in this pull request? The current signal handlers have a subtle bug that stops evaluating registered actions as soon as one of them returns true, this is because `forall` is short-circuited. This PR adds a strict mapping stage before evaluating returned result. There are no known occurrences of the bug and this is a preemptive fix. ## How was this patch tested? As with the original introduction of signal handlers, this was tested manually (unit testing with signals is not straightforward). You can merge this pull request into a Git repository by running: $ git pull https://github.com/jodersky/spark SPARK-10001-hotfix Alternatively you can review and apply these changes as the patch at: https://github.com/apache/spark/pull/12745.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 #12745 commit 7fe0e54c5e39ff942fd58a16d5e5e309887ee883 Author: Jakob OderskyDate: 2016-04-27T22:26:41Z Evaluate all actions in signal handlers (don't short-circuit) --- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org