Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1669#issuecomment-50721673
QA results for PR 1669:br- This patch FAILED unit tests.br- This patch
merges cleanlybr- This patch adds no public classesbrbrFor more
information see test
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/1669#issuecomment-50797594
test 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1669#issuecomment-50798433
QA tests have started for PR 1669. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/17590/consoleFull
---
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1669#issuecomment-50807633
QA results for PR 1669:br- This patch PASSES unit tests.br- This patch
merges cleanlybr- This patch adds no public classesbrbrFor more
information see test
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/1439#issuecomment-50643385
I am worried this PR might have broken testing in Maven:
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/1439#issuecomment-50644241
I am looking at it.
---
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
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/1669#issuecomment-50676098
Oh, clever. This isn't actually what I was suggesting but is a better
solution :) I forgot that createQueryTest could handle multiple sql statements.
---
If your
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/1669#issuecomment-50682859
test 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
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/1669#issuecomment-50698720
test 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
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/1669#issuecomment-50699975
Thank you @yhuai, that seems cool. But can you also remove the old golden
answer file? It should be unused now.
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/1669#issuecomment-50700017
Oh, sorry, I saw that, it renamed.
---
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
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/1669#issuecomment-50715127
Jenkins, test 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/1669#issuecomment-50715565
QA tests have started for PR 1669. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/17556/consoleFull
---
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1439
---
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 yhuai commented on the pull request:
https://github.com/apache/spark/pull/1439#issuecomment-50364539
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 not have this feature
enabled and
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/1439#issuecomment-50374334
Thanks! I've merged this into master.
---
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
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/1439#issuecomment-50425581
@marmbrus seems this PR is still open. Can you double check if it's merged?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/1439#issuecomment-50425995
Apache mirroring is broken. We've filled a bug with infra.
On Jul 28, 2014 6:50 PM, Cheng Hao notificati...@github.com wrote:
@marmbrus
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/1439#issuecomment-50295934
Thank you @yhuai , @liancheng ,I've updated the code according to your
comments, let's see if SparkQA happy with the changes.
---
If your project is set up for
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1439#issuecomment-50295944
QA tests have started for PR 1439. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/17269/consoleFull
---
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1439#issuecomment-50299661
QA results for PR 1439:br- This patch PASSES unit tests.br- This patch
merges cleanlybr- This patch adds the following public classes
(experimental):brclass
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1439#issuecomment-49138252
QA tests have started for PR 1439. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16724/consoleFull
---
22 matches
Mail list logo
