Github user srowen commented on the issue:
https://github.com/apache/spark/pull/15377
Merged 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 this feature
enabled and wishes so, or
Github user lins05 commented on the issue:
https://github.com/apache/spark/pull/15377
@srowen Could we get this merged since the tests are now green? Not sure
why it failed previously, it just turned green without me doing anything.
---
If your project is set up for it, you can
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15377
**[Test build #3372 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3372/consoleFull)**
for PR 15377 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15377
**[Test build #3372 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3372/consoleFull)**
for PR 15377 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15377
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67447/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15377
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/15377
**[Test build #67447 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67447/consoleFull)**
for PR 15377 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15377
**[Test build #67447 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67447/consoleFull)**
for PR 15377 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15377
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67445/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15377
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/15377
**[Test build #67445 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67445/consoleFull)**
for PR 15377 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15377
**[Test build #67445 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67445/consoleFull)**
for PR 15377 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15377
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67394/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15377
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/15377
**[Test build #67394 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67394/consoleFull)**
for PR 15377 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15377
**[Test build #67394 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67394/consoleFull)**
for PR 15377 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15377
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/15377
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67368/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15377
**[Test build #67368 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67368/consoleFull)**
for PR 15377 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15377
**[Test build #67368 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67368/consoleFull)**
for PR 15377 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15377
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67239/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15377
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/15377
**[Test build #67239 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67239/consoleFull)**
for PR 15377 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15377
**[Test build #67239 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67239/consoleFull)**
for PR 15377 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15377
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/15377
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67201/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15377
**[Test build #67201 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67201/consoleFull)**
for PR 15377 at commit
Github user weiqingy commented on the issue:
https://github.com/apache/spark/pull/15377
Not sure why you need to check hadoop.caller.context.enabled" since just
need to make callerContextClassExists be access by test case.
---
If your project is set up for it, you can reply to
Github user lins05 commented on the issue:
https://github.com/apache/spark/pull/15377
@weiqingy Emm, then we would also add the logic of checking
"hadoop.caller.context.enabled" in the test code, which makes the test code
simply duplicates the code path of
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15377
**[Test build #67201 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67201/consoleFull)**
for PR 15377 at commit
Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/15377
LGTM just some minor things.
---
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/15377
@lins05 Maybe something like this:
```
test("Set Spark CallerContext") {
val context = "test"
try {
new CallerContext(context).setCurrentContext()
Github user lins05 commented on the issue:
https://github.com/apache/spark/pull/15377
@weiqingy I agree that's a problem. But i don't see how to unit test the
`callerContextSupported` method without repeating the same logic in the test
code. Do you have any suggestion?
---
If your
Github user weiqingy commented on the issue:
https://github.com/apache/spark/pull/15377
The test case wanted to test âif itâs running on a hadoop version that
supports caller context, our code does set itâ. But in this change , if
somehow the flag was set incorrectly (being
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15377
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67124/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15377
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/15377
**[Test build #67124 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67124/consoleFull)**
for PR 15377 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15377
**[Test build #67124 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67124/consoleFull)**
for PR 15377 at commit
Github user lins05 commented on the issue:
https://github.com/apache/spark/pull/15377
Thanks @jerryshao @srowen . I've updated the code like what you suggested.
---
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 jerryshao commented on the issue:
https://github.com/apache/spark/pull/15377
Yup, that's what I mean.
---
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 srowen commented on the issue:
https://github.com/apache/spark/pull/15377
Yeah, you're saying all the checks can be done upfront? I agree. It will
need a tiny bit of code duplication but is more robust. I think we could also
potentially get rid of the return value from
Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/15377
@srowen I'm not against this change, personally because the usage of flag
is wired to me and frankly saying I haven't seen such pattern in the Spark code.
Since we want to avoid
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/15377
@jerryshao can I take your temperature about how against this change you
are? maybe @lins05 can elaborate again on what this is preventing, and what
happens in case of a race between two threads.
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15377
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/15377
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67039/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15377
**[Test build #67039 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67039/consoleFull)**
for PR 15377 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15377
**[Test build #67039 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67039/consoleFull)**
for PR 15377 at commit
Github user lins05 commented on the issue:
https://github.com/apache/spark/pull/15377
@srowen done.
---
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
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/15377
I think you can avoid it for now, and if that other issue is addressed, it
can go back and use the `Utils` method again everywhere.
---
If your project is set up for it, you can reply to this email
Github user lins05 commented on the issue:
https://github.com/apache/spark/pull/15377
@weiqingy @srowen I see. So do you suggest to avoid using
`Utils.classForName` to get this one merged, or rather wait for SPARK-17714?
---
If your project is set up for it, you can reply to this
Github user weiqingy commented on the issue:
https://github.com/apache/spark/pull/15377
Before 28/Sep/16, using Utils#classForName could pass the PR builder, but
would fail the Spark QA tests in master Maven builds. Unit now (from 28/Sep/16
- now), if there is no change in maven
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/15377
@weiqingy all the Maven/SBT builds pass now, are you sure this is still an
issue? I know the PR builder is just using SBT, yes, but thought we had fixed
this.
---
If your project is set up for it,
Github user weiqingy commented on the issue:
https://github.com/apache/spark/pull/15377
Utils#classForName will make maven build fail, please do not use it before
figure out : https://issues.apache.org/jira/browse/SPARK-17714. The failure is
here:
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15377
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66891/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15377
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/15377
**[Test build #66891 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66891/consoleFull)**
for PR 15377 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15377
**[Test build #66891 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66891/consoleFull)**
for PR 15377 at commit
Github user lins05 commented on the issue:
https://github.com/apache/spark/pull/15377
> Another thing, do you verify it locally? Since there's no unit test to
cover it.
@jerryshao Yeah, I did test it locally to ensure the error is only logged
once.
---
If your project is set
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15377
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/15377
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66885/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15377
**[Test build #66885 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66885/consoleFull)**
for PR 15377 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15377
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66886/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15377
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/15377
**[Test build #66886 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66886/consoleFull)**
for PR 15377 at commit
Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/15377
Another thing, do you verify it locally? Since there's no unit test to
cover it.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15377
**[Test build #66886 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66886/consoleFull)**
for PR 15377 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15377
**[Test build #66885 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66885/consoleFull)**
for PR 15377 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15377
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66719/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15377
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/15377
**[Test build #66719 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66719/consoleFull)**
for PR 15377 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15377
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66715/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15377
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/15377
**[Test build #66715 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66715/consoleFull)**
for PR 15377 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15377
**[Test build #66719 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66719/consoleFull)**
for PR 15377 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15377
**[Test build #66715 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66715/consoleFull)**
for PR 15377 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15377
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66556/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15377
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/15377
**[Test build #66556 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66556/consoleFull)**
for PR 15377 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15377
**[Test build #66556 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66556/consoleFull)**
for PR 15377 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15377
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66506/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15377
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/15377
**[Test build #66506 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66506/consoleFull)**
for PR 15377 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15377
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/15377
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66507/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15377
**[Test build #66507 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66507/consoleFull)**
for PR 15377 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15377
**[Test build #66507 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66507/consoleFull)**
for PR 15377 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15377
**[Test build #66506 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66506/consoleFull)**
for PR 15377 at commit
Github user weiqingy commented on the issue:
https://github.com/apache/spark/pull/15377
Thanks for proposing this PR. 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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15377
**[Test build #66449 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66449/consoleFull)**
for PR 15377 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15377
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66449/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15377
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/15377
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66447/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15377
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/15377
**[Test build #66447 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66447/consoleFull)**
for PR 15377 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15377
**[Test build #66449 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66449/consoleFull)**
for PR 15377 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15377
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66443/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15377
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/15377
**[Test build #66443 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66443/consoleFull)**
for PR 15377 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15377
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66440/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15377
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
1 - 100 of 105 matches
Mail list logo
