Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14589
I see. This is also why I would not have made this change.
---
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
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/14589
@srowen there are bug fixes that are tested by this new harness
(technically not super relevant to this pr though, but all those files are in
the same resources directory).
---
If your project is
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14589
@cloud-fan why backport into a maintenance 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 not have this
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/14589
backport to 2.0!
---
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,
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14589
Seems OK, but src/test/resources was already only a "test data" dir by
nature. I don't think this helped anything.
---
If your project is set up for it, you can reply to this email and have your
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/14589
Thanks - merging in 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/14589
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/14589
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63573/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14589
**[Test build #63573 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63573/consoleFull)**
for PR 14589 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14589
**[Test build #63573 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63573/consoleFull)**
for PR 14589 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14589
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/14589
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63571/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14589
**[Test build #63571 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63571/consoleFull)**
for PR 14589 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14589
**[Test build #63571 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63571/consoleFull)**
for PR 14589 at commit
14 matches
Mail list logo
