That's correct...<br><br>Also, tests that pop up GUI windows and then do "screen analysis" to verify that the test passes will quite often not work well in conjunction with each other if two of them are run simultaneously...
<br><br><br><div><span class="gmail_quote">On 7/25/07, <b class="gmail_sendername">Mathieu Malaterre</b> <<a href="mailto:mathieu.malaterre@gmail.com">mathieu.malaterre@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Alex "hanfei",<br><br> I believe there is nothing in the ADD_TEST to declare dependencies.<br>So chance is that you would run a test (depending on output from<br>another) *before* the dependant test is run.<br>
<br> Is this correct ?<br><br>-Mathieu<br><br>On 7/24/07, Dr. Alex. GOUAILLARD <<a href="mailto:hanfei@caltech.edu">hanfei@caltech.edu</a>> wrote:<br>> hi all,<br>><br>> Annoyed by the time needed by the ITK test suite to run, I made a little
<br>> test trying to use ctest in a multithreaded fashion (thanks to the -I<br>> option). Attached is a little test that is yet neither automatic or<br>> complete, but that already give nice results on windows. It could be
<br>> directly extended to deal with the memcheck command, which would be<br>> great too (as it is even slower).<br>><br>> compile it, copy it in your build directory, and it should work fine.<br>><br>> It first fake running ctest on the first test, for you to read the total
<br>> number of tests. It is then prompting you for that number, and launch 8<br>> threads (you can change that number in the code) each running<br>> MaxNumberOfTest / 8 tests. It prints the logs in files named<br>
> ctest.log.<ThreadNumber><br>><br>> pros:<br>> -> On my 8 cores (2 4-cores) machine the gain is indeed a factor 8. 1012<br>> ITK tests in 5 mn (yum!)<br>><br>> cons:<br>> -> cmake is trying to write on some temp files, and all but the first
<br>> fail to do that.<br>> -> I did not address merging and writing the resulting xml files for<br>> dashboard submission. I need to figure how to redirect each individual<br>> ctest xml output first, then parsing and merging should not really be an
<br>> issue.<br>><br>> questions:<br>> -> how to use ITK framework to make it plateform independent?<br>> -> how to get the number of cores automatically?<br>> -> how to be compliant with the existing 1: writing temp files?
<br>> -> how to be compliant with the existant 2: how to redirect the xml output?<br>><br>> alex "hanfei"<br>><br>> _______________________________________________<br>> CMake mailing list<br>
> <a href="mailto:CMake@cmake.org">CMake@cmake.org</a><br>> <a href="http://www.cmake.org/mailman/listinfo/cmake">http://www.cmake.org/mailman/listinfo/cmake</a><br>><br>><br><br><br>--<br>Mathieu<br>_______________________________________________
<br>CMake mailing list<br><a href="mailto:CMake@cmake.org">CMake@cmake.org</a><br><a href="http://www.cmake.org/mailman/listinfo/cmake">http://www.cmake.org/mailman/listinfo/cmake</a><br></blockquote></div><br>