This is the first I've ever heard of it...<br><br>Cool bug!<br> (that was just a wee bit of sarcasm accompanied by a wry smile...)<br><br>What version of ctest?<br><br>Is this a project that is publicly available, so that I can try to reproduce it here and help these "innocent" coders...?<br>
<br><br>Thanks,<br>David<br><br><br><div class="gmail_quote">On Wed, Apr 20, 2011 at 6:35 PM, Kelly Thompson <span dir="ltr"><<a href="mailto:kgt@lanl.gov">kgt@lanl.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Fellow CMake users:<br>
<br>
I'm having a problem with one of my projects when I run 'ctest -j<N>'. The<br>
problem is that after 70-90 tests, ctest decides to submit all of the<br>
remaining tests at once (~200 tests worth). For example (actual test names<br>
replaced to protect the innocent :-)<br>
<br>
% ctest -j16<br>
Test project /var/tmp/foo<br>
Start 192: testA_2<br>
Start 191: testB_4<br>
Start 190: testC_3<br>
Start 189: testD_2<br>
Start 188: testE_4<br>
1/279 Test #189: testD_2 ................................. Passed<br>
1.81 sec<br>
Start 187: testF_3<br>
2/279 Test #192: testA_2 ................................. Passed<br>
2.98 sec<br>
3/279 Test #191: testB_4 ................................. Passed<br>
2.81 sec<br>
Start 186: testG_2<br>
Start 185: testH_4<br>
4/279 Test #188: testE_4 ................................. Passed<br>
2.81 sec<br>
5/279 Test #190: testC_3 ................................. Passed<br>
2.92 sec<br>
Start 184: testI_3<br>
Start 183: testJ_2<br>
6/279 Test #187: testF_3 ................................. Passed<br>
2.02 sec<br>
Start 182: testK_4<br>
7/279 Test #186: testG_2 ................................. Passed<br>
2.44 sec<br>
<br>
...<br>
<br>
82/279 Test #249: testZA_2 ................................ Passed<br>
8.46 sec<br>
83/279 Test #245: testZB_2 ................................ Passed<br>
3.12 sec<br>
Start 278: testZC_4<br>
84/279 Test #278: testZC_4 ................................ Passed<br>
4.27 sec<br>
Start 266: testZD_4<br>
Start 263: testZE_4<br>
Start 275: testZF_4<br>
Start 270: testZG_4<br>
Start 269: testZH_4<br>
<br>
# ... about 190 tests started all at the same time.<br>
<br>
Start 89: testZZA_1<br>
Start 88: testZZB_1<br>
^C<br>
<br>
These tests are running under mpirun (trailing number indicates number of<br>
cores needed for the test) and so the total load on my machine jumps to<br>
about 400!<br>
<br>
My tests are registered using commands similar to this:<br>
<br>
add_test(<br>
NAME testA_4<br>
COMMAND ${MPIEXEC} ${MPIEXEC_NUMPROC_FLAG} 4<br>
${MPIEXEC_POSTFLAGS}<br>
$<TARGET_FILE:Ut_testA_4_exe><br>
)<br>
set_tests_properties( testA_4<br>
PROPERTIES PROCESSORS "4" )<br>
<br>
Has anyone seen this 'many threads spawning' behavior for ctest (I couldn't<br>
find anything in the bug tracker). Is there a known resolution?<br>
<br>
Thank you,<br>
<br>
-kt<br>
-----<br>
Kelly (KT) Thompson<br>
<a href="mailto:kgt@lanl.gov">kgt@lanl.gov</a><br>
<a href="tel:505.665.8090" value="+15056658090">505.665.8090</a><br>
<br>
Los Alamos National Laboratory<br>
CCS-2, MS D409, TA-3/B-422/R-101<br>
<br>
<br>
_______________________________________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the CMake FAQ at: <a href="http://www.cmake.org/Wiki/CMake_FAQ" target="_blank">http://www.cmake.org/Wiki/CMake_FAQ</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.cmake.org/mailman/listinfo/cmake" target="_blank">http://www.cmake.org/mailman/listinfo/cmake</a><br>
</blockquote></div><br>