Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/14744
LGTM, 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 have this feature
enabled and wishes so,
Github user sun-rui commented on the issue:
https://github.com/apache/spark/pull/14744
LGTM
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14744
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14744
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64685/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14744
**[Test build #64685 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64685/consoleFull)**
for PR 14744 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14744
**[Test build #64685 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64685/consoleFull)**
for PR 14744 at commit
Github user shivaram commented on the issue:
https://github.com/apache/spark/pull/14744
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 have this feature
enabled and
Github user zjffdu commented on the issue:
https://github.com/apache/spark/pull/14744
@shivaram @sun-rui @felixcheung Any more 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/14744
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64413/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14744
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/14744
**[Test build #64413 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64413/consoleFull)**
for PR 14744 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14744
**[Test build #64413 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64413/consoleFull)**
for PR 14744 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14744
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14744
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64391/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14744
**[Test build #64391 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64391/consoleFull)**
for PR 14744 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14744
**[Test build #64391 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64391/consoleFull)**
for PR 14744 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14744
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14744
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64382/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14744
**[Test build #64382 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64382/consoleFull)**
for PR 14744 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14744
**[Test build #64382 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64382/consoleFull)**
for PR 14744 at commit
Github user shivaram commented on the issue:
https://github.com/apache/spark/pull/14744
LGTM. I agree that using SparkConf is preferable over environment variables
-- but it would be good to make the documentation clear on when each option is
used.
---
If your project is set up for
Github user sun-rui commented on the issue:
https://github.com/apache/spark/pull/14744
@felixcheung, I guess that spark conf is preferred over env variable.
---
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 sun-rui commented on the issue:
https://github.com/apache/spark/pull/14744
@zjffdu, basically LGTM
---
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
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/14744
@shivaram @sun-rui thought?
---
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
24 matches
Mail list logo
