[CMake] 2.8.4 order of tests

[David Cole]

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 <byrn at 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 <byrn at 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.cole at kitware.com>
>
>> >> wrote:
>
>> >
>
>> >> > On Thu, Feb 17, 2011 at 3:57 PM, Allen D Byrne <byrn at 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
>
>>