Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/18459
I think strangely enough it's only persisted on failure. I'd just put an
assert false true at the end to verify the test is running, then take it
out and we can merge it. Sound good?
On Wed, Jun 28, 2017 at 4:58 PM Bryan Cutler <[email protected]>
wrote:
> @holdenk <https://github.com/holdenk> @HyukjinKwon
> <https://github.com/hyukjinkwon> any ideas what caused this last error?
> It look like pyspark.sql.tests ran fine, which should have run the Arrow
> tests assuming pyarrow was on the worker but Is there some way to check
> /home/jenkins/workspace/SparkPullRequestBuilder/python/unit-tests.log to
> verify this?
>
> â
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/apache/spark/pull/18459#issuecomment-311824383>, or
mute
> the thread
>
<https://github.com/notifications/unsubscribe-auth/AADp9dB4LjKKOQv6P_V0FMViWf4E3pYPks5sIuiSgaJpZM4OITbk>
> .
>
--
Cell : 425-233-8271
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
