Re: [CMake] 2.8.4 order of tests
On 2011-02-21 12:42-0500 David Cole wrote: This should be fixed already in CMake's 'next' branch. If you can try a nightly installer, or build yourself from 'next', let me know if there is still any problem. Fix will be in 2.8.5 when it comes out in a few months. I got bitten by this bug today in 2.8.4 so I am glad Allen found it earlier, and it will be fixed in 2.8.5. My own use case is I don't particularly care about the order of the tests except that one of them is dependent on most of the rest as I discovered when the tests were run in an unusual order with CMake-2.8.4. Running the set_tests_properties command according to http://cmake.org/cmake/help/cmake-2-8-docs.html#prop_test:DEPENDS works around the issue and is probably a good idea in general when one test depends on others. Note, however, that although most PLplot users are presumably using cmake-2.8.x, PLplot users are still allowed to use cmake-2.6.4 (and that will continue a bit longer). Thus, I had to surround the set_tests_properties command with this CMake version check; if(CMAKE_MAJOR_VERSION EQUAL 2 AND NOT CMAKE_MINOR_VERSION LESS 8) because DEPENDS does not exist in cmake-2.6.x as a test property according to the cmake-2.6.x documentation. Alan __ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); PLplot scientific plotting software package (plplot.org); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __ Linux-powered Science __ ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] 2.8.4 order of tests
One more detail, this seems to be a problem only on non windows (non-make) - windows VS machines ran the tests in correct declaration order. Allen Bug reported: http://public.kitware.com/Bug/view.php?id=11877 On Fri, Feb 18, 2011 at 10:30 AM, David Cole david.c...@kitware.com wrote: Yup. ctest -N and ctest without -N differ in test ordering. Congratulations! You've reported the first regression bug in CMake 2.8.4! :-) I suspect the change for this bug [ http://public.kitware.com/Bug/view.php?id=11561 ] has introduced this issue. I'll make a new issue that we can hopefully address fairly soon. Thanks, David ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] 2.8.4 order of tests
This should be fixed already in CMake's 'next' branch. If you can try a nightly installer, or build yourself from 'next', let me know if there is still any problem. Fix will be in 2.8.5 when it comes out in a few months. Thanks, David On Mon, Feb 21, 2011 at 12:39 PM, Allen D Byrne b...@hdfgroup.org wrote: One more detail, this seems to be a problem only on non windows (non-make) - windows VS machines ran the tests in correct declaration order. Allen Bug reported: http://public.kitware.com/Bug/view.php?id=11877 On Fri, Feb 18, 2011 at 10:30 AM, David Cole david.c...@kitware.com wrote: Yup. ctest -N and ctest without -N differ in test ordering. Congratulations! You've reported the first regression bug in CMake 2.8.4! :-) I suspect the change for this bug [ http://public.kitware.com/Bug/view.php?id=11561 ] has introduced this issue. I'll make a new issue that we can hopefully address fairly soon. Thanks, David ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] 2.8.4 order of tests
Yup. ctest -N and ctest without -N differ in test ordering. Congratulations! You've reported the first regression bug in CMake 2.8.4! :-) I suspect the change for this bug [ http://public.kitware.com/Bug/view.php?id=11561 ] has introduced this issue. I'll make a new issue that we can hopefully address fairly soon. Thanks, David P.S. === The same build tree with a non -N ctest run gives me this: $ ctest Test project /Users/davidcole/tmp/b6 Start 27: enum 1/52 Test #27: enum . Passed0.01 sec Start 28: set_extent 2/52 Test #28: set_extent ... Passed3.66 sec Start 29: getname 3/52 Test #29: getname .. Passed0.06 sec Start 30: vfd 4/52 Test #30: vfd .. Passed0.03 sec Start 31: ntypes 5/52 Test #31: ntypes ... Passed0.17 sec Start 32: dangle 6/52 Test #32: dangle ... Passed0.18 sec Start 33: dtransform 7/52 Test #33: dtransform ... Passed0.02 sec Start 34: reserved 8/52 Test #34: reserved . Passed0.00 sec Start 35: cross_read 9/52 Test #35: cross_read ... Passed0.02 sec Start 36: freespace 10/52 Test #36: freespace Passed0.03 sec Start 37: mf 11/52 Test #37: mf ... Passed0.09 sec ... On Thu, Feb 17, 2011 at 10:41 PM, Allen D Byrne b...@hdfgroup.org wrote: David, I tried ctest -N it lies! Here is the beginning of the test.log showing the problem (peviously the tests were in test number order) : Start testing: Feb 17 21:13 CST -- 435/660 Testing: H5COPY-clear-ext-links 436/660 Testing: H5COPY-ext_link 437/660 Testing: H5COPY-ext_link_f 438/660 Testing: H5COPY-ext_dangle_noobj 439/660 Testing: H5COPY-DIFF_ext_dangle_noobj 440/660 Testing: H5COPY-ext_dangle_noobj_f 441/660 Testing: H5COPY-ext_dangle_nofile 442/660 Testing: H5COPY-DIFF_ext_dangle_nofile 443/660 Testing: H5COPY-ext_dangle_nofile_f 444/660 Testing: H5COPY-ext_link_group 445/660 Testing: H5COPY-ext_link_group_f 446/660 Testing: H5COPY-H5LS_h5copy_extlinks_src 447/660 Testing: H5STAT-h5stat_help1 448/660 Testing: H5STAT-h5stat_help2 449/660 Testing: H5STAT-h5stat_filters 450/660 Testing: H5STAT-h5stat_filters-file 451/660 Testing: H5STAT-h5stat_filters-F 452/660 Testing: H5STAT-h5stat_filters-d 453/660 Testing: H5STAT-h5stat_filters-g 454/660 Testing: H5STAT-h5stat_filters-dT 414/660 Testing: H5COPY-DIFF_grp_nested 415/660 Testing: H5COPY-simple_group 416/660 Testing: H5COPY-DIFF_simple_group 417/660 Testing: H5COPY-grp_rename 418/660 Testing: H5COPY-DIFF_grp_rename 419/660 Testing: H5COPY-grp_dsets_rename 420/660 Testing: H5COPY-DIFF_grp_dsets_rename 421/660 Testing: H5COPY-A_B1_simple 422/660 Testing: H5COPY-DIFF_A_B1_simple 423/660 Testing: H5COPY-A_B2_simple2 424/660 Testing: H5COPY-DIFF_A_B2_simple2 425/660 Testing: H5COPY-C_D_simple 426/660 Testing: H5COPY-DIFF_C_D_simple 427/660 Testing: H5COPY-E_F_grp_dsets 428/660 Testing: H5COPY-DIFF_E_F_grp_dsets 429/660 Testing: H5COPY-G_H_grp_nested 430/660 Testing: H5COPY-DIFF_G_H_grp_nested 431/660 Testing: H5COPY-H5LS_h5copytst 432/660 Testing: H5COPY-clear-refs 433/660 Testing: H5COPY-region_ref 434/660 Testing: H5COPY-H5LS_h5copy_ref 476/660 Testing: H5DUMP-thlink-4 477/660 Testing: H5DUMP-thlink-5 478/660 Testing: H5DUMP-tcomp-1 479/660 Testing: H5DUMP-tcomp-2 480/660 Testing: H5DUMP-tcomp-4 481/660 Testing: H5DUMP-tnestcomp-1 482/660 Testing: H5DUMP-tall-1 483/660 Testing: H5DUMP-tall-2 484/660 Testing: H5DUMP-tall-3 485/660 Testing: H5DUMP-tloop-1 486/660 Testing: H5DUMP-tstr-1 487/660 Testing: H5DUMP-tstr-2 488/660 Testing: H5DUMP-tsaf 489/660 Testing: H5DUMP-tvldtypes1 490/660 Testing: H5DUMP-tvldtypes2 491/660 Testing: H5DUMP-tvldtypes3 492/660 Testing: H5DUMP-tvldtypes4 493/660 Testing: H5DUMP-tvldtypes5 494/660 Testing: H5DUMP-tvlstr 495/660 Testing: H5DUMP-tarray1 455/660 Testing: H5STAT-h5stat_filters-UD 456/660 Testing: H5STAT-h5stat_filters-UT 457/660 Testing: H5STAT-h5stat_tsohm 458/660 Testing: H5STAT-h5stat_newgrat 459/660 Testing: H5STAT-h5stat_newgrat-UG 460/660 Testing: H5STAT-h5stat_newgrat-UA 461/660 Testing: H5DUMP-tgroup-1 462/660 Testing: H5DUMP-tgroup-2 463/660 Testing: H5DUMP-tdset-1 464/660 Testing: H5DUMP-tdset-2 465/660 Testing: H5DUMP-tattr-1 466/660 Testing: H5DUMP-tattr-2 467/660 Testing: H5DUMP-tattr-3 468/660 Testing: H5DUMP-tnamed_dtype_attr 469/660 Testing: H5DUMP-tslink-1 470/660 Testing: H5DUMP-tudlink-1 471/660 Testing: H5DUMP-tslink-2 472/660 Testing: H5DUMP-tudlink-2 473/660 Testing: H5DUMP-thlink-1 474/660 Testing:
Re: [CMake] 2.8.4 order of tests
Bug reported: http://public.kitware.com/Bug/view.php?id=11877 On Fri, Feb 18, 2011 at 10:30 AM, David Cole david.c...@kitware.com wrote: Yup. ctest -N and ctest without -N differ in test ordering. Congratulations! You've reported the first regression bug in CMake 2.8.4! :-) I suspect the change for this bug [ http://public.kitware.com/Bug/view.php?id=11561 ] has introduced this issue. I'll make a new issue that we can hopefully address fairly soon. Thanks, David P.S. === The same build tree with a non -N ctest run gives me this: $ ctest Test project /Users/davidcole/tmp/b6 Start 27: enum 1/52 Test #27: enum . Passed 0.01 sec Start 28: set_extent 2/52 Test #28: set_extent ... Passed 3.66 sec Start 29: getname 3/52 Test #29: getname .. Passed 0.06 sec Start 30: vfd 4/52 Test #30: vfd .. Passed 0.03 sec Start 31: ntypes 5/52 Test #31: ntypes ... Passed 0.17 sec Start 32: dangle 6/52 Test #32: dangle ... Passed 0.18 sec Start 33: dtransform 7/52 Test #33: dtransform ... Passed 0.02 sec Start 34: reserved 8/52 Test #34: reserved . Passed 0.00 sec Start 35: cross_read 9/52 Test #35: cross_read ... Passed 0.02 sec Start 36: freespace 10/52 Test #36: freespace Passed 0.03 sec Start 37: mf 11/52 Test #37: mf ... Passed 0.09 sec ... On Thu, Feb 17, 2011 at 10:41 PM, Allen D Byrne b...@hdfgroup.org wrote: David, I tried ctest -N it lies! Here is the beginning of the test.log showing the problem (peviously the tests were in test number order) : Start testing: Feb 17 21:13 CST -- 435/660 Testing: H5COPY-clear-ext-links 436/660 Testing: H5COPY-ext_link 437/660 Testing: H5COPY-ext_link_f 438/660 Testing: H5COPY-ext_dangle_noobj 439/660 Testing: H5COPY-DIFF_ext_dangle_noobj 440/660 Testing: H5COPY-ext_dangle_noobj_f 441/660 Testing: H5COPY-ext_dangle_nofile 442/660 Testing: H5COPY-DIFF_ext_dangle_nofile 443/660 Testing: H5COPY-ext_dangle_nofile_f 444/660 Testing: H5COPY-ext_link_group 445/660 Testing: H5COPY-ext_link_group_f 446/660 Testing: H5COPY-H5LS_h5copy_extlinks_src 447/660 Testing: H5STAT-h5stat_help1 448/660 Testing: H5STAT-h5stat_help2 449/660 Testing: H5STAT-h5stat_filters 450/660 Testing: H5STAT-h5stat_filters-file 451/660 Testing: H5STAT-h5stat_filters-F 452/660 Testing: H5STAT-h5stat_filters-d 453/660 Testing: H5STAT-h5stat_filters-g 454/660 Testing: H5STAT-h5stat_filters-dT 414/660 Testing: H5COPY-DIFF_grp_nested 415/660 Testing: H5COPY-simple_group 416/660 Testing: H5COPY-DIFF_simple_group 417/660 Testing: H5COPY-grp_rename 418/660 Testing: H5COPY-DIFF_grp_rename 419/660 Testing: H5COPY-grp_dsets_rename 420/660 Testing: H5COPY-DIFF_grp_dsets_rename 421/660 Testing: H5COPY-A_B1_simple 422/660 Testing: H5COPY-DIFF_A_B1_simple 423/660 Testing: H5COPY-A_B2_simple2 424/660 Testing: H5COPY-DIFF_A_B2_simple2 425/660 Testing: H5COPY-C_D_simple 426/660 Testing: H5COPY-DIFF_C_D_simple 427/660 Testing: H5COPY-E_F_grp_dsets 428/660 Testing: H5COPY-DIFF_E_F_grp_dsets 429/660 Testing: H5COPY-G_H_grp_nested 430/660 Testing: H5COPY-DIFF_G_H_grp_nested 431/660 Testing: H5COPY-H5LS_h5copytst 432/660 Testing: H5COPY-clear-refs 433/660 Testing: H5COPY-region_ref 434/660 Testing: H5COPY-H5LS_h5copy_ref 476/660 Testing: H5DUMP-thlink-4 477/660 Testing: H5DUMP-thlink-5 478/660 Testing: H5DUMP-tcomp-1 479/660 Testing: H5DUMP-tcomp-2 480/660 Testing: H5DUMP-tcomp-4 481/660 Testing: H5DUMP-tnestcomp-1 482/660 Testing: H5DUMP-tall-1 483/660 Testing: H5DUMP-tall-2 484/660 Testing: H5DUMP-tall-3 485/660 Testing: H5DUMP-tloop-1 486/660 Testing: H5DUMP-tstr-1 487/660 Testing: H5DUMP-tstr-2 488/660 Testing: H5DUMP-tsaf 489/660 Testing: H5DUMP-tvldtypes1 490/660 Testing: H5DUMP-tvldtypes2 491/660 Testing: H5DUMP-tvldtypes3 492/660 Testing: H5DUMP-tvldtypes4 493/660 Testing: H5DUMP-tvldtypes5 494/660 Testing: H5DUMP-tvlstr 495/660 Testing: H5DUMP-tarray1 455/660 Testing: H5STAT-h5stat_filters-UD 456/660 Testing: H5STAT-h5stat_filters-UT 457/660 Testing: H5STAT-h5stat_tsohm 458/660 Testing: H5STAT-h5stat_newgrat 459/660 Testing: H5STAT-h5stat_newgrat-UG 460/660 Testing: H5STAT-h5stat_newgrat-UA 461/660 Testing: H5DUMP-tgroup-1 462/660 Testing: H5DUMP-tgroup-2 463/660 Testing: H5DUMP-tdset-1 464/660 Testing: H5DUMP-tdset-2 465/660 Testing: H5DUMP-tattr-1 466/660 Testing: H5DUMP-tattr-2 467/660 Testing: H5DUMP-tattr-3 468/660 Testing: H5DUMP-tnamed_dtype_attr 469/660 Testing: H5DUMP-tslink-1
Re: [CMake] 2.8.4 order of tests
On Thu, Feb 17, 2011 at 3:57 PM, Allen D Byrne b...@hdfgroup.org wrote: I just installed 2.8.4 and on my fedora 14 linux box the ctest -D Experimental stage decided to run the tests in some unknown to me order. The previous versions always ran them in order of definition. Any thing I can do to get the ordering back? Allen ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake Delete the file Testing/Temporary/CTestCostData.txt in your build tree. It saves run times from run to run and orders them as slowest first on subsequent runs. A clean build (no CostData file) without any parallel testing, and without any test COST properties defined should give you the top to bottom ordering that you're used to. Saving this data from run to run helps us schedule parallel testing jobs efficiently on subsequent runs. HTH, David ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] 2.8.4 order of tests
On Thu, Feb 17, 2011 at 4:08 PM, David Cole david.c...@kitware.com wrote: On Thu, Feb 17, 2011 at 3:57 PM, Allen D Byrne b...@hdfgroup.org wrote: I just installed 2.8.4 and on my fedora 14 linux box the ctest -D Experimental stage decided to run the tests in some unknown to me order. The previous versions always ran them in order of definition. Any thing I can do to get the ordering back? Allen ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake Delete the file Testing/Temporary/CTestCostData.txt in your build tree. It saves run times from run to run and orders them as slowest first on subsequent runs. A clean build (no CostData file) without any parallel testing, and without any test COST properties defined should give you the top to bottom ordering that you're used to. Saving this data from run to run helps us schedule parallel testing jobs efficiently on subsequent runs. HTH, David Having said all that: if your goal is to order certain tests with respect to each other, see the help for the test property DEPENDS: http://cmake.org/cmake/help/cmake-2-8-docs.html#prop_test:DEPENDS ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] 2.8.4 order of tests
This was from a clean build folder. And I just want the test to run in the order defined in the CMakeLists.txt files. Also never had set any COST properties. The surprise was that this never happened before. Allen On Thu, Feb 17, 2011 at 4:08 PM, David Cole david.c...@kitware.com wrote: On Thu, Feb 17, 2011 at 3:57 PM, Allen D Byrne b...@hdfgroup.org wrote: I just installed 2.8.4 and on my fedora 14 linux box the ctest -D Experimental stage decided to run the tests in some unknown to me order. The previous versions always ran them in order of definition. Any thing I can do to get the ordering back? Allen ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake Delete the file Testing/Temporary/CTestCostData.txt in your build tree. It saves run times from run to run and orders them as slowest first on subsequent runs. A clean build (no CostData file) without any parallel testing, and without any test COST properties defined should give you the top to bottom ordering that you're used to. Saving this data from run to run helps us schedule parallel testing jobs efficiently on subsequent runs. HTH, David Having said all that: if your goal is to order certain tests with respect to each other, see the help for the test property DEPENDS: http://cmake.org/cmake/help/cmake-2-8-docs.html#prop_test:DEPENDS ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] 2.8.4 order of tests
On Thu, Feb 17, 2011 at 4:20 PM, Allen D Byrne b...@hdfgroup.org wrote: This was from a clean build folder. And I just want the test to run in the order defined in the CMakeLists.txt files. Also never had set any COST properties. The surprise was that this never happened before. Allen On Thu, Feb 17, 2011 at 4:08 PM, David Cole david.c...@kitware.com wrote: On Thu, Feb 17, 2011 at 3:57 PM, Allen D Byrne b...@hdfgroup.org wrote: I just installed 2.8.4 and on my fedora 14 linux box the ctest -D Experimental stage decided to run the tests in some unknown to me order. The previous versions always ran them in order of definition. Any thing I can do to get the ordering back? Allen ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake Delete the file Testing/Temporary/CTestCostData.txt in your build tree. It saves run times from run to run and orders them as slowest first on subsequent runs. A clean build (no CostData file) without any parallel testing, and without any test COST properties defined should give you the top to bottom ordering that you're used to. Saving this data from run to run helps us schedule parallel testing jobs efficiently on subsequent runs. HTH, David Having said all that: if your goal is to order certain tests with respect to each other, see the help for the test property DEPENDS: http://cmake.org/cmake/help/cmake-2-8-docs.html#prop_test:DEPENDS So there is no Testing/Temporary/CTestCostData.txt file at the time you call ctest -D Experimental? Can you point me to a source tree that I can build that demonstrates this behavior? If you are not running tests in parallel and you have no cost data (in the form of a cached file or properties set) then the tests should run in the same top-to-bottom order that they always have. Thx, David ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] 2.8.4 order of tests
Just using standard gcc/gfortran on the fedora distro. It is the 64bit version? You can grab one of our recent src tarballs from http://www.hdfgroup.org/ftp/HDF5/hdf5-1.8.6/; Allen PS. I will be out of touch for the next 36 hours On Thu, Feb 17, 2011 at 4:20 PM, Allen D Byrne b...@hdfgroup.org wrote: This was from a clean build folder. And I just want the test to run in the order defined in the CMakeLists.txt files. Also never had set any COST properties. The surprise was that this never happened before. Allen On Thu, Feb 17, 2011 at 4:08 PM, David Cole david.c...@kitware.com wrote: On Thu, Feb 17, 2011 at 3:57 PM, Allen D Byrne b...@hdfgroup.org wrote: I just installed 2.8.4 and on my fedora 14 linux box the ctest -D Experimental stage decided to run the tests in some unknown to me order. The previous versions always ran them in order of definition. Any thing I can do to get the ordering back? Allen ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake Delete the file Testing/Temporary/CTestCostData.txt in your build tree. It saves run times from run to run and orders them as slowest first on subsequent runs. A clean build (no CostData file) without any parallel testing, and without any test COST properties defined should give you the top to bottom ordering that you're used to. Saving this data from run to run helps us schedule parallel testing jobs efficiently on subsequent runs. HTH, David Having said all that: if your goal is to order certain tests with respect to each other, see the help for the test property DEPENDS: http://cmake.org/cmake/help/cmake-2-8-docs.html#prop_test:DEPENDS So there is no Testing/Temporary/CTestCostData.txt file at the time you call ctest -D Experimental? Can you point me to a source tree that I can build that demonstrates this behavior? If you are not running tests in parallel and you have no cost data (in the form of a cached file or properties set) then the tests should run in the same top-to-bottom order that they always have. Thx, David ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] 2.8.4 order of tests
After building HDF5 v 1.8.6 on my Mac, I get this: $ ctest -N Test project /Users/davidcole/tmp/b6 Test #1: testhdf5 Test #2: accum Test #3: lheap Test #4: ohdr Test #5: stab Test #6: gheap Test #7: pool Test #8: hyperslab Test #9: istore Test #10: bittests Test #11: dt_arith Test #12: dtypes Test #13: dsets Test #14: cmpd_dset Test #15: extend Test #16: external Test #17: objcopy Test #18: links Test #19: unlink Test #20: big Test #21: mtime Test #22: fillval Test #23: mount Test #24: flush1 Test #25: flush2 Test #26: app_ref Test #27: enum Test #28: set_extent Test #29: getname Test #30: vfd Test #31: ntypes Test #32: dangle Test #33: dtransform Test #34: reserved Test #35: cross_read Test #36: freespace Test #37: mf Test #38: btree2 Test #39: fheap Test #40: error_test Test #41: err_compat Test #42: tcheck_version Test #43: testmeta Test #44: cache Test #45: cache_api Test #46: ttsafe Test #47: h5perf_serial Test #48: chunk Test #49: iopipe Test #50: overhead Test #51: perf_meta Test #52: zip_perf Total Tests: 52 I'm not familiar enough with HDF5 to know if this is correct or not. Is this the same order you're seeing? Or can you tell me your expected order? I'll try to analyze the source tree and figure out what's going on, but what you expect will tell me something, too. Thanks, David On Thu, Feb 17, 2011 at 5:10 PM, Allen D Byrne b...@hdfgroup.org wrote: Just using standard gcc/gfortran on the fedora distro. It is the 64bit version? You can grab one of our recent src tarballs from http://www.hdfgroup.org/ftp/HDF5/hdf5-1.8.6/; Allen PS. I will be out of touch for the next 36 hours On Thu, Feb 17, 2011 at 4:20 PM, Allen D Byrne b...@hdfgroup.org wrote: This was from a clean build folder. And I just want the test to run in the order defined in the CMakeLists.txt files. Also never had set any COST properties. The surprise was that this never happened before. Allen On Thu, Feb 17, 2011 at 4:08 PM, David Cole david.c...@kitware.com wrote: On Thu, Feb 17, 2011 at 3:57 PM, Allen D Byrne b...@hdfgroup.org wrote: I just installed 2.8.4 and on my fedora 14 linux box the ctest -D Experimental stage decided to run the tests in some unknown to me order. The previous versions always ran them in order of definition. Any thing I can do to get the ordering back? Allen ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake Delete the file Testing/Temporary/CTestCostData.txt in your build tree. It saves run times from run to run and orders them as slowest first on subsequent runs. A clean build (no CostData file) without any parallel testing, and without any test COST properties defined should give you the top to bottom ordering that you're used to. Saving this data from run to run helps us schedule parallel testing jobs efficiently on subsequent runs. HTH, David Having said all that: if your goal is to order certain tests with respect to each other, see the help for the test property DEPENDS: http://cmake.org/cmake/help/cmake-2-8-docs.html#prop_test:DEPENDS So there is no Testing/Temporary/CTestCostData.txt file at the time you call ctest -D Experimental? Can you point me to a source tree that I can build that demonstrates this behavior? If you are not running tests in parallel and you have no cost data (in the form of a cached file or properties set) then the tests should run in the same top-to-bottom order that they always have. Thx, David ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] 2.8.4 order of tests
On Thu, 17 Feb 2011 17:21:22 -0500, David Cole said: I'm not familiar enough with HDF5 to know if this is correct or not. Is this the same order you're seeing? Or can you tell me your expected order? I'll try to analyze the source tree and figure out what's going on, but what you expect will tell me something, too. Perhaps you guys are actually talking about this:??? http://public.kitware.com/Bug/view.php?id=11746 -- Sean McBride, B. Eng s...@rogue-research.com Rogue Researchwww.rogue-research.com Mac Software Developer Montréal, Québec, Canada ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] 2.8.4 order of tests
On Thu, Feb 17, 2011 at 5:25 PM, Sean McBride s...@rogue-research.com wrote: On Thu, 17 Feb 2011 17:21:22 -0500, David Cole said: I'm not familiar enough with HDF5 to know if this is correct or not. Is this the same order you're seeing? Or can you tell me your expected order? I'll try to analyze the source tree and figure out what's going on, but what you expect will tell me something, too. Perhaps you guys are actually talking about this:??? http://public.kitware.com/Bug/view.php?id=11746 I doubt it because he's talking about doing a ctest -D Experimental which would not have any -j associated with it -- Sean McBride, B. Eng s...@rogue-research.com Rogue Research www.rogue-research.com Mac Software Developer Montréal, Québec, Canada ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
