[yt-dev] Answer testing

Stephen Skory s at skory.us
Thu Feb 14 09:32:38 PST 2013


+1 on 2.

On Thu, Feb 14, 2013 at 10:10 AM, Britton Smith <brittonsmith at gmail.com> wrote:
> +1 on 2.
>
> On Feb 14, 2013 12:08 PM, "Sam Skillman" <samskillman at gmail.com> wrote:
>>
>> +1 on (2)
>>
>>
>> On Thu, Feb 14, 2013 at 10:00 AM, Matthew Turk <matthewturk at gmail.com>
>> wrote:
>>>
>>> Hi all,
>>>
>>> Currently we run all unit and answer tests on every push.  Running answer
>>> testing, particularly with FLASH data, takes a long time.  (Sidenote:
>>> FLASH in
>>> 2.x is particularly bad for large data objects, which answer testing
>>> does.)
>>> This will get worse once Orion and Chombo have been added.  I think we're
>>> looking at up to 15 minutes per run.  This has two effects:
>>>
>>> 1) Changes which break unit tests take longer to get reported.
>>> 2) We'll go through our ShiningPanda monthly allocation quite quickly.
>>>
>>> There are two solutions that I see:
>>>
>>> 1) Buy more time on ShiningPanda
>>> 2) Only run answer testing at most once a day, but still run unit tests
>>> on every
>>> push.
>>>
>>> My proposal is to go with #2 with the backup of #1 as needed.  Can I get
>>> [+-]1
>>> on this?
>>>
>>> -Matt
>>> _______________________________________________
>>> yt-dev mailing list
>>> yt-dev at lists.spacepope.org
>>> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>>
>>
>>
>> _______________________________________________
>> yt-dev mailing list
>> yt-dev at lists.spacepope.org
>> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>>
>
> _______________________________________________
> yt-dev mailing list
> yt-dev at lists.spacepope.org
> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>



--
Stephen Skory
s at skory.us
http://stephenskory.com/
510.621.3687 (google voice)



More information about the yt-dev mailing list