[Insight-users] How to run the tests on the local machine?

Luis Ibanez luis.ibanez at kitware.com
Thu Sep 29 18:00:30 EDT 2005


Hi Ashis,

Thanks for letting us know of your success with executing the tests.

As you pointed out, a number of ITK filters will take advantage of
multiple processors when they are available. Other tests, will have
lower usage, specially when image IO is involved.

The list of failing tests that you posted seems to be consistent with
the failing test resported in another similar 64 bit platform running
at Briham and Women's Hospital:

                   smyslov.­bwh.­harvard.

http://www.itk.org/Testing/Sites/smyslov.bwh.harvard.edu/Linux-x86_64-debug-icc-9.0/20050929-0100-Nightly/Test.html


You may want to make your test a Nightly by simply adding a scheduled
task that will run


                ctest -D Nightly


from your binary directory.

Note that this will CVS update your ITK source tree every night, and
therefore you shouldn't use that binary tree for other applications
that you may be developing.

In other word, you probably want to have two different builds in your
machine, one for contributing to the Nightly Dashboard, and the other
one, more stable, for using it as the ITK library for your applications.


   Regards,


      Luis


---------------------
Ashish Poddar wrote:
> Hi Luis,
> 
> thanks for the guidelines, and I really appreciate your patience in such 
> matters!
> 
> I ran the tests on the binaries compiled through the "mixed" version of 
> header files (which is still not very reliable) in the win xp x64 
> environment running on dual Xeon Processor 3.7 GHz. I was very pleased 
> to see the CPU usage going up to 93% during some of the tests (I think 
> was the algorithm test) which gave an indication that both the 
> processors are being utilized by ITK... but on other tests, only 25% of 
> the machine was utilized (though it was running a 64-bit application!)..
> 
> one of the tests (itkGDCMSeriesReadImageWrite.exe) generated an 
> unhandled exception..
> 
> total time it took to complete all the tests was about 25 minutes.
> 
> the detailed results can be found be this link....
> http://dl002.filefactory.com/get/i.php?f=8a20c43a567a0354f03df6f4&b=9&c=483867528d2bc926 
> <http://dl002.filefactory.com/get/i.php?f=8a20c43a567a0354f03df6f4&b=9&c=483867528d2bc926>
> 
> with best regards,
> Ashish.
> 
> <Summary>
> 96% tests passed, 41 tests failed out of 1022
> 
> The following tests FAILED:
> 
>      55 - vnl_test_math (Failed)
>     227 - itkImageLinearIteratorTest (Failed)
>     309 - itkVectorImageTest (Failed)
>     517 - itkAccumulateImageFilterTest (Failed)
>     521 - itkBinaryThresholdImageFilterTest2 (Failed)
>     532 - itkSimpleContourExtractorImageFilterTest (Failed)
>     674 - itkVnlFFTTest (Failed)
>     707 - itkNrrdImageIOTest1 (Failed)
>     708 - itkNrrdImageIOTest2 (Failed)
>     717 - itkVectorImageReadWriteTest2 (Failed)
>     748 - itkDicomDifficultFile (Failed)
>     789 - itkGDCMImageIOTest3 (Failed)
>     790 - itkGDCMImageIOTest4 (Failed)
>     791 - itkGDCMSeriesReadImageWrite (SEGFAULT)
>     792 - itkNrrdImageReadWriteTest1 (Failed)
>     793 - itkNrrdImageReadWriteTest2 (Failed)
>     794 - itkNrrdImageReadWriteTest3 (Failed)
>     795 - itkNrrdImageReadWriteTest4 (Failed)
>     796 - itkNrrdImageReadWriteTest5 (Failed)
>     797 - itkNrrdImageReadWriteTest6 (Failed)
>     798 - itkNrrdImageReadWriteTest7 (Failed)
>     799 - itkNrrdImageReadWriteTest8 (Failed)
>     800 - itkNrrdImageReadWriteTest9 (Failed)
>     801 - itkNrrdImageReadWriteTest10 (Failed)
>     802 - itkNrrdImageReadWriteTest11 (Failed)
>     803 - itkNrrdRGBImageReadWriteTest0 (Failed)
>     804 - itkNrrdRGBImageReadWriteTest1 (Failed)
>     805 - itkNrrdRGBImageReadWriteTest2 (Failed)
>     806 - itkNrrdRGBAImageReadWriteTest (Failed)
>     807 - itkNrrdDiffusionTensor3DImageReadTest1 (Failed)
>     808 - itkNrrdDiffusionTensor3DImageReadTest2 (Failed)
>     809 - itkNrrdDiffusionTensor3DImageReadTest3 (Failed)
>     810 - itkNrrdDiffusionTensor3DImageReadWriteTest (Failed)
>     811 - itkNrrdComplexImageReadTest (Failed)
>     812 - itkNrrdComplexImageReadWriteTest (Failed)
>     813 - itkNrrdVectorImageReadTest (Failed)
>     814 - itkNrrdVectorImageReadWriteTest (Failed)
>     815 - itkNrrdCovariantVectorImageReadTest (Failed)
>     816 - itkNrrdCovariantVectorImageReadWriteTest (Failed)
>     838 - ImageLinearIteratorWithIndexTest (Failed)
>     968 - MultiResImageRegistration2Test (Failed)
> 
> </Summary>
> 
> 
> 
> On 9/28/05, *Luis Ibanez* < luis.ibanez at kitware.com 
> <mailto:luis.ibanez at kitware.com>> wrote:
> 
>     Hi Ashish,
> 
>     Just open a MSDOS window, go to your binary
>     directory and type:
> 
> 
>                      ctest
> 
> 
>     That should be enough...
> 
>     Ctest will run all the tests for  you.
> 
>     Ctest is an executable that makes part of CMake. If it is not
>     in your path, you usually will find it on
> 
> 
>         c:\Program Files\CMake20\bin\ctest.exe
> 
>     (unless, of course, you built it on your own in a different
>     directory)
> 
>     For a full list of instructions on how to use ctest and how
>     to run the testing suite please refer to the following Wiki page
> 
> 
>         http://www.cmake.org/Wiki/CMake_Testing_With_CTest
> 
>     In particular to
> 
>     http://www.cmake.org/Wiki/CMake_Testing_With_CTest#Running_Individual_Tests
> 
> 
> 
>        Regards,
> 
> 
>           Luis
> 
> 
>     ---------------------
>     Ashish Poddar wrote:
>      > Hi,
>      >
>      > I apologize if the question is too obvious, but I cant figure out
>     the
>      > way to run the tests on local machine... is there a batch file or
>     do i
>      > have to create one for running the tests..
>      >
>      > I have compiled the ITK library and want to run the tests on win
>     XP x64
>      > machine... compiled by using platform SDK by microsoft.
>      >
>      > with regards,
>      > Ashish.
>      >
>      > --
>      > Ashish Poddar
>      > Its high time we standardize everything!
>      > Y:ashish_poddar | MSN:ashish_poddar at yahoo.com
>     <mailto:MSN:ashish_poddar at yahoo.com>
>      > <mailto:MSN <mailto:MSN>:ashish_poddar at yahoo.com
>     <mailto:ashish_poddar at yahoo.com>> | gTalk:ahpoddar+talk at gmail.com
>     <mailto:gTalk:ahpoddar+talk at gmail.com>
>      > <mailto:gTalk <mailto:gTalk>:ahpoddar+talk at gmail.com
>     <mailto:ahpoddar+talk at gmail.com>>
>      >
>      >
>      >
>     ------------------------------------------------------------------------
> 
>      >
>      > _______________________________________________
>      > Insight-users mailing list
>      > Insight-users at itk.org <mailto:Insight-users at itk.org>
>      > http://www.itk.org/mailman/listinfo/insight-users
> 
> 
> 
> 
> -- 
> Ashish Poddar
> Its high time we standardize everything!
> Y:ashish_poddar | MSN:ashish_poddar at yahoo.com 
> <mailto:MSN:ashish_poddar at yahoo.com> | gTalk:ahpoddar+talk at gmail.com 
> <mailto:gTalk:ahpoddar+talk at gmail.com>
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Insight-users mailing list
> Insight-users at itk.org
> http://www.itk.org/mailman/listinfo/insight-users



More information about the Insight-users mailing list