From spencer.graves at prodsyse.com  Wed Sep 19 20:57:32 2012
From: spencer.graves at prodsyse.com (Spencer Graves)
Date: Wed, 19 Sep 2012 11:57:32 -0700
Subject: [Rd] CRAN test / avoidance
In-Reply-To: <CABdHhvEDZTU_Wum4jKbf3Y+EbH6udm=Ts09TraCLxiRMjDo=dQ@mail.gmail.com>
References: <mailman.29.1348048809.29913.r-devel@r-project.org>
	<5059D1F8.1070501@mayo.edu> <5059DF74.3070200@gmail.com>
	<CABdHhvEDZTU_Wum4jKbf3Y+EbH6udm=Ts09TraCLxiRMjDo=dQ@mail.gmail.com>
Message-ID: <505A159C.1020303@prodsyse.com>

On 9/19/2012 11:51 AM, Hadley Wickham wrote:
>> 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.


       I raised the question, because CRAN maintainers rejected the 
latest version of "fda" because some of the examples took too long to 
run on their computers.


       Spencer

>
> Hadley
>


-- 
Spencer Graves, PE, PhD
President and Chief Technology Officer
Structure Inspection and Monitoring, Inc.
751 Emerson Ct.
San Jos?, CA 95126
ph:  408-655-4567
web:  www.structuremonitoring.com



[Rd] CRAN test / avoidance
Spencer Graves