Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/7139#issuecomment-127664838
@brkyvz I think I figured out the problem with Jenkins -- Since Jenkins
uses SBT it doesn't build the SparkR package at the beginning along with the
rest of the artifacts and only builds SparkR while running SparkR unit tests.
So what ends up happening is that R/lib doesn't exist when the core unit tests
are running.
I think the right thing to do here is to get Jenkins to build SparkR along
with other components. @JoshRosen and @yu-iskw were discussing a similar issue
in #7883. For now can we just comment out the test and open a JIRA to
un-comment it once we fix this ?
---
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
