Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/11970
---
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 vanzin commented on the pull request:
https://github.com/apache/spark/pull/11970#issuecomment-203634249
Merging to master (so I can fix my other PR that conflicts with this one).
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11970#issuecomment-203627806
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/11970#issuecomment-203627803
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11970#issuecomment-203627150
**[Test build #54544 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54544/consoleFull)**
for PR 11970 at commit
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/11970#issuecomment-203590449
it would be nice if we had one util function for figuring out scala version
but I didn't look to see how much change is needed for that so optional.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11970#issuecomment-203569688
**[Test build #54544 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54544/consoleFull)**
for PR 11970 at commit
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/11970#issuecomment-203569415
@tgravescs @andrewor14
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11970#issuecomment-201655218
Test FAILed.
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/11970#issuecomment-201655216
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11970#issuecomment-201654857
**[Test build #54236 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54236/consoleFull)**
for PR 11970 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11970#issuecomment-201596034
**[Test build #54236 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54236/consoleFull)**
for PR 11970 at commit
GitHub user vanzin opened a pull request:
https://github.com/apache/spark/pull/11970
[SPARK-13955] [yarn] Also look for Spark jars in the build directory.
Move the logic to find Spark jars to CommandBuilderUtils and make it
available for YARN code, so that it's possible to
13 matches
Mail list logo
