You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We already inced the time limit to the max 50 minutes. But we quite often now hit that walltime, and more than 30 mins is spent just installing stuff.
We tried to use ubuntu binariers for some stuff instead, but this was a much worse option because the package versions were often much too old.
I currently have to start like every second build again, to randomly avoid the time barrier, and we are thinking about setting up our own CI server -- which at least I would like to avoid if there is no need.
But this is beginning to hurt.
Any hints? I mean most of this could be somehow cached right?
The text was updated successfully, but these errors were encountered:
I've convinced Travis to use binary packages from the cran2deb PPA
(https://launchpad.net/~marutter/+archive/ubuntu/c2d4u). A complete
travis build now takes around 20m, down from ~40m. I've simply copied
all packages from Imports and Suggests to the travis yaml. Some
packages are currently not available on the PPA (those are commented
out), others are outdated. To deal with outdated packages, I wrote a
small update-packages script specifically for travis (travis uses two
libraries and R does not support that in any useful way).
Summed up, this is the relevant part of what is going on on travis to
set up the check environment:
Installation of R including base and recommended packages, plus
some extra stuff like texlive and pandoc
Installation of binary packages listed in r_binary_packages
(including deps) to the system lib
Installation of github packages listed in r_github_packages
(including deps, if not already installed) to the user lib
Installation of (additional) dependencies for mlr to the user lib
via devtools::install_deps(). This also updates many packages
(although the documentation does not feature this).
Hi,
here at mlr we currently have a problem that our build takes too long.
https://travis-ci.org/berndbischl/mlr
We already inced the time limit to the max 50 minutes. But we quite often now hit that walltime, and more than 30 mins is spent just installing stuff.
We tried to use ubuntu binariers for some stuff instead, but this was a much worse option because the package versions were often much too old.
I currently have to start like every second build again, to randomly avoid the time barrier, and we are thinking about setting up our own CI server -- which at least I would like to avoid if there is no need.
But this is beginning to hurt.
Any hints? I mean most of this could be somehow cached right?
The text was updated successfully, but these errors were encountered: