[Insight-developers] PatchBasedDenoising test timeouts

[Matt McCormick]

On Tue, Oct 9, 2012 at 4:50 PM, David Doria <daviddoria at gmail.com> wrote:
> On Tue, Oct 9, 2012 at 12:48 PM, Kris Zygmunt <krismz at sci.utah.edu> wrote:
>> Hi,
>>    Are there any release builds that are timing out or only debug builds?
>> Also, what is the default timeout set to?  I see some builds fail timeout
>> when the time is 16m 40s, others fail and report the time is about 25 m.
>> Does the test environment stop the test when timeout is exceeded or just
>> note the time after completions.  I get a little confused on CDash because
>> it will say Status: FAILED, Time Status PASSED, and Details: Completed
>> (Timeout).  Would it make more sense to just allow a larger timeout value
>> when in debug build or even optionally disable some of the tests for a debug
>> build?
>> -Kris
>
> Is it not possible to reduce the size of the problem that this is
> tested on? The test suite takes an extremely long time to run as is,
> so tests that take tens of minutes should be avoided if possible.

Yes, we should either optimize the code or change the test datasets so
that they run more quickly.  The CDash timeout failures are a concern,
but it is even more important to keep the test suite nimble for
development purposes.

Thanks,
Matt