Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16256
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16256
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/16256
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70039/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16256
**[Test build #70039 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70039/consoleFull)**
for PR 16256 at commit
Github user ajbozarth commented on the issue:
https://github.com/apache/spark/pull/16256
Also in case the others are on vacation, @vanzin want to take a look too?
---
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 issue:
https://github.com/apache/spark/pull/16256
**[Test build #70039 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70039/consoleFull)**
for PR 16256 at commit
Github user ajbozarth commented on the issue:
https://github.com/apache/spark/pull/16256
@srowen and @tgravescs could you take a quick look at this fix for a bug
@yhuai found
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as