[Insight-developers] PatchBasedDenoising test timeouts

[Kris Zygmunt]

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

On Oct 5, 2012, at 9:19 AM, Matt McCormick wrote:

> On Fri, Oct 5, 2012 at 3:05 PM, Bradley Lowekamp <blowekamp at mail.nih.gov 
> > wrote:
>> Matt,
>>
>> Another outstanding dashboard issue is the patch based denoising  
>> filters timing out on many systems. What do you think is the best  
>> thing to do about that?
>>
>
> Yes, I completely agree.  I think it should be a priority.
>
> It looks like this patch helped things:
>
>  http://review.source.kitware.com/#/c/6194/
>
> The next step is to cache operator() access?  Kris, do you have time
> to look at this?
>
> Thanks,
> Matt