[Insight-developers] run memtest in multithreaded ?

[Karthik Krishnan]

Thanks

Increase the DART_TESTING_TIMEOUT variable, while configuring using 
cmake.. the default is 1500 s, before dart kills the test.


Gaetan Lehmann wrote:

>
> Hi,
>
> I have splitted the tests in to parts. It now runs in about 16h. There 
> is  no memory problem while running 2 valgrinds at the same time, but 
> there is  some timeouts:
>
>          82 - itkGoodnessOfFitMixtureModelCostFunctionTest (Timeout)
>         244 - itkLevelSetFunctionTest (Timeout)
>         378 - itkContourMeanDistanceImageFilterTest (Timeout)
>         526 - itkAdaptiveHistogramEqualizationImageFilterTest (Timeout)
>         528 - itkAdaptiveHistogramEqualizationImageFilterTest2 (Timeout)
>         588 - itkCannySegmentationLevelSetImageFilterTest (Timeout)
>         592 - itkDemonsRegistrationFilterTest (Timeout)
>         606 - 
> itkGeodesicActiveContourShapePriorLevelSetImageFilterTest_2  (Timeout)
>         630 - itkImageRegistrationMethodTest_16 (Timeout)
>         636 - 
> itkKullbackLeiblerCompareHistogramImageToImageMetricTest  (Timeout)
>         640 - itkMattesMutualInformationImageToImageMetricTest (Timeout)
>         974 - ImageRegistration2Test (Timeout)
>         978 - ImageRegistration5Test2 (Timeout)
>         980 - ImageRegistration7Test (Timeout)
>         984 - ImageRegistration14Test (Timeout)
>         990 - DeformableRegistration2Test (Timeout)
>         992 - DeformableRegistration4Test (Timeout)
>         994 - DeformableRegistration6Test (Timeout)
>         1024 - GeodesicActiveContourShapePriorCallosumTest (Timeout)
>
>          87 - itkImageToHistogramGeneratorTest (Timeout)
>         103 - itkSampleSelectiveMeanShiftBlurringFilterTest (Timeout)
>         435 - itkInterpolateImagePointsFilterTest (Timeout)
>         603 - itkFEMRegistrationFilterTest (Timeout)
>         629 - itkImageRegistrationMethodTest_15 (Timeout)
>         645 - itkMRIBiasFieldCorrectionFilterTest (Timeout)
>         649 - itkMultiResolutionPDEDeformableRegistrationTest (Timeout)
>         667 - itkRegionGrow2DTest (Timeout)
>         689 - itkSymmetricForcesDemonsRegistrationFilterTest (Timeout)
>         971 - ImageRegistration5oTest2 (Timeout)
>         981 - ImageRegistration9Test (Timeout)
>         985 - ImageRegistration15Test (Timeout)
>         991 - DeformableRegistration3Test (Timeout)
>         993 - DeformableRegistration5Test (Timeout)
>         1019 - CellularSegmentation1Test (Timeout)
>
> Is it possible to increase available time for those tests ?
>
> Thanks,
>
> Gaetan
>
>
> On Fri, 23 Sep 2005 21:29:10 +0200, Karthik Krishnan  
> <Karthik.Krishnan at kitware.com> wrote:
>
>> Something to look forward to in the future maybe :)
>>
>> http://www.vtk.org/Wiki/ITK_Roadmap_2005_2006
>>
>> "Add Support for parallel testing in CTest"
>> This will make possible to launch multiple test simultaneously from  
>> CTest. In this way, users with multiprocessor machines will be able 
>> to  reduce the time needed for running the test suite.
>>
>>
>> For now, you can just run memory tests every nth day or limit to 
>> every  nth test...
>> http://www.itk.org/Testing/Sites/Sabbath.kitware/Linux-g++-3.4-Shared/20050923-0100-Nightly/Notes.html 
>>
>>
>> Regards
>> karthik
>>
>> Gaetan Lehmann wrote:
>>
>>> Hi,
>>>
>>> I'm trying to run the full memory test. This test is very long 
>>> (more  than 24h): it will be a problem to run it each day ;-).
>>> I have noticed that only one proc is used during the test, so is 
>>> there  something to do to use the 2 processors ?
>>>
>>> Thanks,
>>>
>>> Gaetan
>>>   
>>> ------------------------------------------------------------------------ 
>>>
>>>
>>> _______________________________________________
>>> Insight-developers mailing list
>>> Insight-developers at itk.org
>>> http://www.itk.org/mailman/listinfo/insight-developers
>>>
>
>
>