Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9134#issuecomment-150654820
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9134#issuecomment-150654821
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9134#issuecomment-150654718
**[Test build #44232 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44232/consoleFull)**
for PR 9134 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9134#issuecomment-150546888
Hm, it still sounds like it's more of an artifact of mixing build
artifacts. Something is being loaded that _was_ compiled with Hive support, but
then finds it's
Github user zjffdu commented on the pull request:
https://github.com/apache/spark/pull/9134#issuecomment-150551129
Yes, that would be encountered as developer
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9134#issuecomment-150630290
Merged build started.
---
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 yhuai commented on the pull request:
https://github.com/apache/spark/pull/9134#issuecomment-150630038
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9134#issuecomment-150630263
Merged build triggered.
---
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 yhuai commented on the pull request:
https://github.com/apache/spark/pull/9134#issuecomment-150630025
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/9134#issuecomment-150632179
**[Test build #44232 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44232/consoleFull)**
for PR 9134 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9134#issuecomment-150749295
**[Test build #44286 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44286/consoleFull)**
for PR 9134 at commit
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/9134#issuecomment-150748520
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 yhuai commented on the pull request:
https://github.com/apache/spark/pull/9134#issuecomment-150760079
Thanks! Merging to 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 does not have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9134#issuecomment-150759945
**[Test build #44286 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44286/consoleFull)**
for PR 9134 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9134#issuecomment-150759983
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9134#issuecomment-150759982
Merged build finished. Test PASSed.
---
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/9134
---
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/9134#issuecomment-150748614
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9134#issuecomment-150748611
Merged build triggered.
---
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 zjffdu commented on the pull request:
https://github.com/apache/spark/pull/9134#issuecomment-150736740
Seems the failed test is not related
---
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/9134#issuecomment-150181092
@zjffdu given your similar PR on this topic, can you address the question
of how this occurs? The "Error" is a different lower-level thing.
---
If your project is set
Github user zjffdu commented on the pull request:
https://github.com/apache/spark/pull/9134#issuecomment-150392534
Here's how to reproduce the issue.
1. export SPARK_PREPEND_CLASSES=true
2. Build spark with command: build/sbt assembly -Pyarn -Phadoop-2.6 -Phive
22 matches
Mail list logo
