Github user rberenguel commented on the issue:
https://github.com/apache/spark/pull/18164
@ueshin @HyukjinKwon thanks for giving it a very thorough look and sorry
for my previous comment, that was terribly unclear. I was confused because the
Appveyor tick mark was green for commit 076ebed and I had run the tests
locally (forgot linting, though), so I was pretty sure the test was right and I
was confused about how the subset wrong still had a passing test.
I probably skipped the wrong step for testing the Python tests (I'm still
figuring out which corners I can cut to avoid a full compile/build cycle for
the whole project, which takes ages for me) so I didn't see my local test
failing, but the remote one was more puzzling, I guess appveyor had a hiccup
here. Sorry again for the confused and confusing statements above :)
---
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 the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
