Github user ConeyLiu commented on the issue:
https://github.com/apache/spark/pull/18830
Thank you all.
---
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 cloud-fan commented on the issue:
https://github.com/apache/spark/pull/18830
LGTM, merging to master/2.2
---
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/18830
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/18830
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80316/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18830
**[Test build #80316 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80316/testReport)**
for PR 18830 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18830
**[Test build #80316 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80316/testReport)**
for PR 18830 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18830
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 ConeyLiu commented on the issue:
https://github.com/apache/spark/pull/18830
Thanks for reviewing. Hi @jiangxb1987, seems the test didn't triggered.
---
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 jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/18830
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 jerryshao commented on the issue:
https://github.com/apache/spark/pull/18830
Nice catch, 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
Github user ConeyLiu commented on the issue:
https://github.com/apache/spark/pull/18830
@cloud-fan @vanzin Would you mind take a lookï¼ Thanks a lot.
---
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
Github user ConeyLiu commented on the issue:
https://github.com/apache/spark/pull/18830
You can see here
[L208](https://github.com/apache/spark/blob/master/core/src/main/scala/org/apache/spark/storage/DiskBlockObjectWriter.scala#L208),
when we called 'revertPartialWritesAndClose',
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18830
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
13 matches
Mail list logo
