Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Native R on Travis takes longer than the script #147

Open
robertzk opened this issue Feb 26, 2015 · 7 comments
Open

Native R on Travis takes longer than the script #147

robertzk opened this issue Feb 26, 2015 · 7 comments

Comments

@robertzk
Copy link

screen shot 2015-02-26 at 10 55 35 am

On my packages, building using the new native R support takes 3-4x as long as using the old method. Is it possible to incorporate a .travis.yml flag to install just base R to speed up this time?

@eddelbuettel
Copy link
Contributor

Same here on a first test with one of the the most minimal CRAN packages I have. I had tuned my .travis.yml carefully to be as lightweight as possible; the way things stand right now the new default seems useful for newbs but I guess I will cook my own (making things like texlive, pandoc, automated addition of two apt-get repos etc pp all optional).

So now that r-travis has proved the concept, maybe time to move on and fork into something simpler, lighter, faster. Or really urge them to get on with it with prebuilt images.

@eddelbuettel
Copy link
Contributor

In a nutshell, what happened was:

  • while we all worked on r-travis, we made sure certain "API" access points were optional
  • now latex, devtools, ... are forced in unconditionally

and in sum everything seems to take several minutes minutes longer.

@craigcitro
Copy link
Owner

yes, this is by design: we unconditionally install latex and pandoc, and no longer set the R CMD check options to skip vignettes.

but don't worry, this is all part of a plan: now that we're merged into travis, we're looking at getting ourselves a base image with all of these bits pre-installed. then we'll have fast builds with all the various tools available.

and if you're wondering why i didn't leave it all optional to start: i didn't want to introduce a whole collection of configuration options that were slated to go away from the start, making deprecating them later potentially more complicated.

@craigcitro
Copy link
Owner

(i'm going to leave this open for other folks who come looking.)

@ehrlinger
Copy link

My package compiles a vignette with LaTeX, but still fails on Travis because of missing latex packages. Is there an option to either install the missing xcolor or booktabs packages in LaTeX? Or alternatively, skip the vignettes?

@eddelbuettel
Copy link
Contributor

Sure:

  • I have been skipping vignette builds since the start as it takes so long to set it up
  • If you want to build with vignettes and need extra packages, use the apt-get hook to install those.

@ehrlinger
Copy link

Got it working again... with:

apt_packages:
  - texlive-full

May have been brute force, but it succeeds. Of course, it also makes Travis run LONGER, but it's all automated anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants