Github user mgaido91 commented on the issue:
https://github.com/apache/spark/pull/18731
I close this, I will prepare a new PR, cleaner. Thanks
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For ad
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18731
Build finished. Test FAILed.
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18731
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81696/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18731
**[Test build #81696 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81696/testReport)**
for PR 18731 at commit
[`a53404e`](https://github.com/apache/spark/commit/a
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18731
**[Test build #81696 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81696/testReport)**
for PR 18731 at commit
[`a53404e`](https://github.com/apache/spark/commit/a5
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/18731
Thanks! Will review it this weekend
---
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
enab
Github user mgaido91 commented on the issue:
https://github.com/apache/spark/pull/18731
AppVeyor build failed because of a timeout. I don't know how to retest it.
---
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 mgaido91 commented on the issue:
https://github.com/apache/spark/pull/18731
The CI error actually is a timeout. I don't know the reason of the timeout
or how to retrigger it. If I should do anything please just tell me.
If there is anything I can do for this PR just tel
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18731
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18731
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81183/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18731
**[Test build #81183 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81183/testReport)**
for PR 18731 at commit
[`fdd21eb`](https://github.com/apache/spark/commit/f
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18731
**[Test build #81183 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81183/testReport)**
for PR 18731 at commit
[`fdd21eb`](https://github.com/apache/spark/commit/fd
Github user mgaido91 commented on the issue:
https://github.com/apache/spark/pull/18731
@gatorsmile any feedback on this?
I added the support for all the corrupt record handling modes and I added
the relative tests.
Is anything else needed?
---
If your project is set up for i
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18731
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80271/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18731
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/18731
**[Test build #80271 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80271/testReport)**
for PR 18731 at commit
[`6071daf`](https://github.com/apache/spark/commit/6
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18731
**[Test build #80271 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80271/testReport)**
for PR 18731 at commit
[`6071daf`](https://github.com/apache/spark/commit/60
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18731
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80251/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18731
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
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18731
**[Test build #80251 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80251/testReport)**
for PR 18731 at commit
[`0a2e8c4`](https://github.com/apache/spark/commit/0
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18731
**[Test build #80251 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80251/testReport)**
for PR 18731 at commit
[`0a2e8c4`](https://github.com/apache/spark/commit/0a
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/18731
BTW, you also need to add a few error handling test cases to ensure the
corrupted record handling works.
---
If your project is set up for it, you can reply to this email and have your
reply app
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18731
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79963/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18731
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/18731
**[Test build #79963 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79963/testReport)**
for PR 18731 at commit
[`4da8493`](https://github.com/apache/spark/commit/4
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18731
**[Test build #79963 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79963/testReport)**
for PR 18731 at commit
[`4da8493`](https://github.com/apache/spark/commit/4d
Github user mgaido91 commented on the issue:
https://github.com/apache/spark/pull/18731
The reason of the UT failure is that in these two UTs we are passing
invalid JSONs (mind the extra closed curly brace):
-
https://github.com/apache/spark/blob/master/sql/core/src/test/scal
Github user mgaido91 commented on the issue:
https://github.com/apache/spark/pull/18731
I am debugging, thanks.
---
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
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/18731
Could you fix the bug?
---
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 wishe
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18731
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79938/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18731
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
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18731
**[Test build #79938 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79938/testReport)**
for PR 18731 at commit
[`972a28d`](https://github.com/apache/spark/commit/9
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18731
**[Test build #79938 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79938/testReport)**
for PR 18731 at commit
[`972a28d`](https://github.com/apache/spark/commit/97
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/18731
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 if
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/18731
Thanks for fixing it! Will review it this weekend.
---
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 t
Github user mgaido91 commented on the issue:
https://github.com/apache/spark/pull/18731
cc @gatorsmile
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18731
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 feat
37 matches
Mail list logo
