Github user tejasapatil commented on the issue:
https://github.com/apache/spark/pull/15605
This is superseded by https://github.com/apache/spark/pull/19054 Closing
---
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 tejasapatil commented on the issue:
https://github.com/apache/spark/pull/15605
@hvanhovell @cloud-fan @gatorsmile @yhuai : Any opinions about the approach
described in my previous comment ?
---
If your project is set up for it, you can reply to this email and have your
Github user tejasapatil commented on the issue:
https://github.com/apache/spark/pull/15605
Most of the tests are failing because `ShuffleExchange` currently does not
handle `PartitioningCollection`. That can be fixed but as I looked at this
more, I found a flaw in the current
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15605
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15605
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67460/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15605
**[Test build #67460 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67460/consoleFull)**
for PR 15605 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15605
**[Test build #67460 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67460/consoleFull)**
for PR 15605 at commit
Github user tejasapatil commented on the issue:
https://github.com/apache/spark/pull/15605
@hvanhovell : It got closed accidentally. There are test case failures that
I have to still debug. Happy to hear any comments about the approach.
---
If your project is set up for it, you can
Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/15605
@tejasapatil this didn't work?
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15605
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/15605
**[Test build #67431 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67431/consoleFull)**
for PR 15605 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15605
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67431/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15605
**[Test build #67431 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67431/consoleFull)**
for PR 15605 at commit
Github user tejasapatil commented on the issue:
https://github.com/apache/spark/pull/15605
cc @hvanhovell
---
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,
14 matches
Mail list logo
