Tracking time spent on R CMD check
lcolladotor opened this issue · comments
Timing request
As originally discussed in #119 (comment), it would be useful to track time spent on the R CMD check. This information is needed prior to submitting a package to Bioconductor (see Package guidelines correctness) but could in general be of interest to all R package developers.
One way to do it
This can be done using the time command and is information you don't get when using R CMD check --timings. From Travis CI, you get an upper bound on the time since it reports the time spent on ./travis-tool.sh run_tests which includes the R CMD build step.
But... what time to use?
My main doubt is that I do not know which machine is used to get that 5 minute mark for Bioconductor packages. For instance, my package derfinder took ~270 secs to check on my 3yr old laptop at this commit but took ~400 secs in Travis as seen here.
Oh well, if you get it under 5 minutes using a Travis worker, then you should be fine either way.
Anyhow, it should be a small change and it provides useful information.
Solved in r-builder by separating the build and check steps metacran/r-builder#10 (comment)