Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/1968#issuecomment-53629945
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 marmbrus commented on the pull request:
https://github.com/apache/spark/pull/1968#issuecomment-53633660
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 marmbrus commented on the pull request:
https://github.com/apache/spark/pull/1968#issuecomment-53636038
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1968#issuecomment-53647798
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19338/consoleFull)
for PR 1968 at commit
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/1968#issuecomment-53648090
Thanks! I've merged this into master and 1.1
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/1968
---
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 liancheng commented on the pull request:
https://github.com/apache/spark/pull/1968#issuecomment-53524211
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
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/1968#issuecomment-53524202
The build failure was caused by unrelated streaming test suites.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/1968#issuecomment-53359760
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 marmbrus commented on the pull request:
https://github.com/apache/spark/pull/1968#issuecomment-53363685
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/1968#issuecomment-53363914
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19180/consoleFull)
for PR 1968 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1968#issuecomment-53369942
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19180/consoleFull)
for PR 1968 at commit
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/1968#issuecomment-52889655
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
Github user luogankun commented on the pull request:
https://github.com/apache/spark/pull/1968#issuecomment-52880789
@liancheng Now I need to do what?
---
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
Github user luogankun commented on the pull request:
https://github.com/apache/spark/pull/1968#issuecomment-52445779
@marmbrus From the console log, unit tests failed causes not my case, but
hive thrift server.
---
If your project is set up for it, you can reply to this email and
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/1968#issuecomment-52446501
It's the Kerberos issue again. Thrift server test suites pass when executed
separately, but fail non-deterministically when executed with other tests. I
guess they're
16 matches
Mail list logo
