Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/7883#issuecomment-127415539
Other than downloading the thing that bothers me is that lintr has 33
dependencies which all get downloaded and built from source (you can see the
log file I linked to above to see what I mean). Given all the existing
flakiness with builds I don't want to introduce a new source of flakiness
How about this for a solution -- In the Jenkins machine, we ask @shaneknapp
to install from devtools github now. In the lint-r script we check if the
package is available and if not we re-install from devtools. BTW in the future
we can extend this to check for a specific lintr version / git-hash if we want
a specific version. Does that sound good ?
---
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]
