Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5679#issuecomment-96618907
[Test build #716 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/716/consoleFull)
for PR 5679 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/5679#issuecomment-96618838
Jenkins has trouble posting this back, but it failed unit tests, however
this seems to be for unrelated reasons. Let me try again.
---
If your project is set up for it,
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5679#issuecomment-96657002
[Test build #716 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/716/consoleFull)
for PR 5679 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/5679
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5679#issuecomment-96766677
Can one of the admins verify this patch?
---
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
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/5679#issuecomment-96365916
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5679#issuecomment-96454919
[Test build #714 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/714/consoleFull)
for PR 5679 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5679#issuecomment-96286235
[Test build #705 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/705/consoleFull)
for PR 5679 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5679#issuecomment-96288688
[Test build #705 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/705/consoleFull)
for PR 5679 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/5679#issuecomment-96195182
ok to test
---
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
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/5679#discussion_r29041189
--- Diff: core/src/main/scala/org/apache/spark/SparkContext.scala ---
@@ -1055,7 +1055,7 @@ class SparkContext(config: SparkConf) extends Logging
with
GitHub user stevencanopy opened a pull request:
https://github.com/apache/spark/pull/5679
SPARK-7103: Fix crash with SparkContext.union when RDD has no partitioner
Added a check to the SparkContext.union method to check that a partitioner
is defined on all RDDs when instantiating a
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5679#issuecomment-95810737
Can one of the admins verify this patch?
---
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
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/5679#issuecomment-96058807
Jenkins, test his please. This LGTM
---
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
14 matches
Mail list logo
