Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/17044
Thanks. Merging 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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17044
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73869/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17044
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/17044
**[Test build #73869 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73869/testReport)**
for PR 17044 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17044
**[Test build #73869 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73869/testReport)**
for PR 17044 at commit
Github user marmbrus commented on the issue:
https://github.com/apache/spark/pull/17044
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 zsxwing commented on the issue:
https://github.com/apache/spark/pull/17044
@tdas could you take a look?
---
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 vanzin commented on the issue:
https://github.com/apache/spark/pull/17044
@zsxwing I'm not the right person to review this, but can we get the ball
rolling on this fix? This test is really flaky and constantly causes PR
builders to fail.
---
If your project is set up
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17044
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73369/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17044
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/17044
**[Test build #73369 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73369/testReport)**
for PR 17044 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17044
**[Test build #73369 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73369/testReport)**
for PR 17044 at commit
12 matches
Mail list logo
