Github user tdas commented on the issue:
https://github.com/apache/spark/pull/15396
I am merging this to master and 2.1
---
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 an
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15396
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72002/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15396
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
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15396
**[Test build #72002 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72002/testReport)**
for PR 15396 at commit
[`9878c9f`](https://github.com/apache/spark/commit/9
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15396
**[Test build #72002 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72002/testReport)**
for PR 15396 at commit
[`9878c9f`](https://github.com/apache/spark/commit/98
Github user neggert commented on the issue:
https://github.com/apache/spark/pull/15396
Any update on this? Would love to see it in an upcoming release.
---
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 andrewor14 commented on the issue:
https://github.com/apache/spark/pull/15396
Looks good. I left a suggestion that I think will make the code cleaner.
---
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 pr
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15396
Can you reference the earlier pull requests here 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 project does not have this
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15396
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66538/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15396
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
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15396
**[Test build #66538 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66538/consoleFull)**
for PR 15396 at commit
[`22d16b4`](https://github.com/apache/spark/commit/
Github user jkbradley commented on the issue:
https://github.com/apache/spark/pull/15396
I'm no expert on checkpointing, but the tests look fine to me. You could
eliminated duplicated code in the tests by putting the shared code in a helper
method.
Tested locally to confirm
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15396
**[Test build #66538 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66538/consoleFull)**
for PR 15396 at commit
[`22d16b4`](https://github.com/apache/spark/commit/2
13 matches
Mail list logo
