From h.wickham at gmail.com  Wed Sep 19 20:51:09 2012
From: h.wickham at gmail.com (Hadley Wickham)
Date: Wed, 19 Sep 2012 13:51:09 -0500
Subject: [Rd] CRAN test / avoidance
In-Reply-To: <5059DF74.3070200@gmail.com>
References: <mailman.29.1348048809.29913.r-devel@r-project.org>
	<5059D1F8.1070501@mayo.edu> <5059DF74.3070200@gmail.com>
Message-ID: <CABdHhvEDZTU_Wum4jKbf3Y+EbH6udm=Ts09TraCLxiRMjDo=dQ@mail.gmail.com>

> The question becomes: how does information get passed along to indicate
> things that may take a long time to run. The discussion so far has focused
> on developers setting, or using, some flags to indicate tests and examples
> that take a long time. Another option would be to have the check/build
> process generate a file with information about the time it took to run
> tests, vignettes, and examples, probably with some information about the
> speed of the machine it was run on. Then CRAN and anyone else that wants to
> run tests can take this information into consideration.

To paraphrase Uwe (fortunes::fortune(192)): computing is cheap and
thinking hurts.

I don't understand why we are spending so much time discussing what
probably amounts (at most) to a couple of thousand of dollars of
compute time.

Hadley

-- 
RStudio / Rice University
http://had.co.nz/



[Rd] CRAN test / avoidance
Hadley Wickham