Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/7919#issuecomment-127491163
This is also related to https://github.com/apache/spark/pull/7826
Yes, I agree this can't be related. The 'test' of this line being removed
has already passed in this
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/7919
---
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/7919#issuecomment-127454694
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 tedyu opened a pull request:
https://github.com/apache/spark/pull/7919
[BUILD] Remove dependency reduced POM hack
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tedyu/spark master
Alternatively you can review and
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7919#issuecomment-127454892
[Test build #39633 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/39633/consoleFull)
for PR 7919 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7919#issuecomment-127473138
[Test build #39633 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/39633/console)
for PR 7919 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7919#issuecomment-127473170
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 tedyu commented on the pull request:
https://github.com/apache/spark/pull/7919#issuecomment-127478076
The PySpark test failure should not be related to the change.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
