Github user shaneknapp commented on the issue:
https://github.com/apache/spark/pull/15821
@holdenk yeah, another set of eyes would be great! i haven't actually
touched the test infra code in a long time and i'm currently wrapping my brain
around the order of operations that run-pip-tests goes through in conjunction
w/everything else.
i have a feeling that the chain of scripts (run-tests-jenkins ->
run-tests-jenkins.py -> run-tests -> run-pip-tests) besides being confusing for
humans (ie: me), is also fragile WRT conda envs (aka munging PATH) in our
environment.
would installing pyarrow 0.4.0 in the py3k conda env fix things? if so, i
can bang that out in moments.
---
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]
