Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1906#issuecomment-51932732
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 pro
GitHub user copester opened a pull request:
https://github.com/apache/spark/pull/1906
[SPARK-1766] sorted functions to meet pedantic requirements
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ResilientScience/spark master
Alte
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1859
---
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 enab
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1859#issuecomment-51700839
QA results for PR 1859:- This patch PASSES unit tests.- This patch
merges cleanly- This patch adds no public classesFor more
information see test
ouptut:https://amplab.c
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1859#issuecomment-51699932
QA tests have started for PR 1859. This patch merges cleanly. View
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18262/consoleFull
---
If
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1859#issuecomment-51699849
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 hav
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1859#issuecomment-51680113
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 hav
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1859#issuecomment-51678860
QA results for PR 1859:- This patch FAILED unit tests.- This patch
merges cleanly- This patch adds no public classesFor more
information see test
ouptut:https://amplab.c
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1859#issuecomment-51678150
QA tests have started for PR 1859. This patch merges cleanly. View
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18243/consoleFull
---
If
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1859#issuecomment-51678093
Jenkins, test this please. LGTM... pedantry is encouraged.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1859#issuecomment-51655492
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 pro
GitHub user copester opened a pull request:
https://github.com/apache/spark/pull/1859
[SPARK-1766] sorted functions to meet pedantic requirements
Pedantry is underrated
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ResilientScie
12 matches
Mail list logo
