On Mon, 28 Feb 2011, Prof Brian Ripley wrote:
Unfortunately it would need a major rewrite, and either piping output through a pager (surely the standard Unix way to handle this) or redirecting to a file is the simplest way to do this. R CMD check calls a process to run .runPackageTestsR, which calls further processes to run each test and diff the results. We could simply capture stdout/stderr of .runPackageTestsR, but then one would have to wait until all the tests had run before seeing any output, which may mean waiting hours -- that was decided to be too undesirable.
I've implemented in R-devel something that copies the output on a per-test basis to 00check.log. It may not be perfect (in particular if a test crashes its R process badly enough), but it will at least record a test-by-test summary of success/failure.
On Fri, 25 Feb 2011, Terry Therneau wrote:
It would be nice if the 00check.log file also included this part of the output: Running ?bladder.R? Comparing ?bladder.Rout? to ?bladder.Rout.save? ... OK Running ?book1.R? Comparing ?book1.Rout? to ?book1.Rout.save? ... OK Running ?book2.R? Comparing ?book2.Rout? to ?book2.Rout.save? ... OK etc. The survival package has enough test scripts that it exceeds my terminal's scroll bar; I have to either watch closely or run R CMD check survival >& mylog
The most prolix are
survival portfolio matlab kappalab spatstat
68 36 32 30 28
BB HSAUR2 fields pcalg aster
26 22 22 22 21
The remedy seems to be to group the tests into larger units.
Terry Therneau
-- Brian D. Ripley, ripley at stats.ox.ac.uk Professor of Applied Statistics, http://www.stats.ox.ac.uk/~ripley/ University of Oxford, Tel: +44 1865 272861 (self) 1 South Parks Road, +44 1865 272866 (PA) Oxford OX1 3TG, UK Fax: +44 1865 272595
Brian D. Ripley, ripley at stats.ox.ac.uk Professor of Applied Statistics, http://www.stats.ox.ac.uk/~ripley/ University of Oxford, Tel: +44 1865 272861 (self) 1 South Parks Road, +44 1865 272866 (PA) Oxford OX1 3TG, UK Fax: +44 1865 272595