I'm allocating time to clean out the last few Dashboard errors on the BeOS builds, and I've noticed that I've started getting "timeouts" in the test process.
It'll update from CVS and try to rebuild CMake, and fail to build almost instantly (it prints "There was a timeout" to the console when run with -VV). Then all tests fail as "not run" since the binaries it wants never got built.
Current CVS works when built by hand with the bootstrap script and "make" from the command line. "make test" passes all tests. It's only when having ctest run the Dashboard script that this happens.
It also doesn't happen if I use a cmake/ctest that I built a few months ago...then I only have the usual handful of errors I originally set out to fix...so it's something that changed in the past few weeks at most.
Is there some new variable that current ctest expects to be set, or is this a deeper, BeOS-specific bug? The testProcess programs all work, including the ones that test timeouts.
Dashboard script I used is this: http://www.cmake.org/Testing/Sites/IcculusDotOrgBeOS/beos5pemax-gcc2.9-991026/20070211-0100-Nightly/Notes.html Thanks, --ryan. _______________________________________________ CMake mailing list [email protected] http://www.cmake.org/mailman/listinfo/cmake
