Github user weiqingy commented on the issue:
https://github.com/apache/spark/pull/15563
Thanks a lot for the review, @tgravescs @mridulm
---
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 mridulm commented on the issue:
https://github.com/apache/spark/pull/15563
Merging 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 does not have this feature
enabled and wishes so,
Github user mridulm commented on the issue:
https://github.com/apache/spark/pull/15563
Looks good to me
---
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
Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/15563
+1. @mridulm you have any further comments?
---
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 issue:
https://github.com/apache/spark/pull/15563
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68437/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15563
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 project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15563
**[Test build #68437 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68437/consoleFull)**
for PR 15563 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15563
**[Test build #68437 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68437/consoleFull)**
for PR 15563 at commit
Github user tdas commented on the issue:
https://github.com/apache/spark/pull/15563
jenkins, 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
enabled and wishes so, or
Github user weiqingy commented on the issue:
https://github.com/apache/spark/pull/15563
@mridulm @tgravescs It seems Jenkins doesn't work?
---
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 tgravescs commented on the issue:
https://github.com/apache/spark/pull/15563
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 this feature
enabled and
Github user mridulm commented on the issue:
https://github.com/apache/spark/pull/15563
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 this feature
enabled and
Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/15563
please look at jenkins failures
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15563
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 project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15563
**[Test build #68340 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68340/consoleFull)**
for PR 15563 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15563
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68340/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15563
**[Test build #68340 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68340/consoleFull)**
for PR 15563 at commit
Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/15563
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 this feature
enabled and
Github user weiqingy commented on the issue:
https://github.com/apache/spark/pull/15563
Hi, @tgravescs Could you please review this PR? Thanks.
---
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 weiqingy commented on the issue:
https://github.com/apache/spark/pull/15563
Hadoop verifies caller contexts passed in
Github user weiqingy commented on the issue:
https://github.com/apache/spark/pull/15563
@rxin Thanks for reviewing this. I have updated the PR not to make this as
a spark-submit argument.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15563
Can't this just be a normal sparkconf? Why do we need to specialize the
spark-submit arguments for this?
---
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 issue:
https://github.com/apache/spark/pull/15563
Can one of the admins verify this patch?
---
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
23 matches
Mail list logo
