[CMake] CMake test suite - 51% failure rate?! (x86/Solaris 10)

Bill Hoffman hoffman.mlist at gmail.com
Mon Mar 26 15:32:06 EST 2007


Matthew Woehlke wrote:
> A while back I "successfully"* built CMake on an x86/Solaris 10 box. 
> Now, trying to build on a different box, I am getting a 51% failure 
> rate in the test suite. Huh?!
>
> (* the test suite has an odd problem with GNU make 3.81, otherwise it 
> was clean)
>
> I also can't seem to find any output from the failed tests, which were:
>          15 - CommandLineTest (Failed)
>          16 - TarTest (Failed)
>          19 - CustComDepend (Failed)
>          20 - CustomCommand (Failed)
>          22 - FindPackageTest (Failed)
>          23 - SystemInformation (Failed)
>          24 - StringFileTest (Failed)
>          25 - MathTest (Failed)
>          27 - simple (Failed)
>          28 - OutOfSource (Failed)
>          29 - PreOrder (Failed)
>          31 - CxxOnly (Failed)
>          33 - SimpleInstall (Failed)
>          34 - SimpleInstall-Stage2 (Failed)
>          36 - LoadedCommand (Failed)
>          37 - LoadedCommandOneConfig (Failed)
>          38 - complex (Failed)
>          39 - complexOneConfig (Failed)
>          40 - Example (Failed)
>          41 - TutorialStep1 (Failed)
>          42 - TutorialStep2 (Failed)
>          43 - TutorialStep3 (Failed)
>          44 - TutorialStep4 (Failed)
>          45 - TutorialStep5 (Failed)
>          46 - testing (Failed)
>          47 - wrapping (Failed)
>          48 - testdriver1 (Failed)
>          49 - testdriver2 (Failed)
>          50 - testdriver3 (Failed)
>          56 - JumpWithLibOut (Failed)
>          57 - JumpNoLibOut (Failed)
>          61 - ExternalOBJ (Failed)
>          62 - kwsys (Failed)
>          63 - SubDir (Failed)
>
> Ideas? The most obvious difference I can think of is that a different 
> compiler is being used in this case ("Sun C 5.8 2005/10/13", also 
> there is a(n ancient!) gcc 2.95.3 available) versus the box where 
> CMake tested OK ("Sun C 5.7 2005/01/07", no gcc available).
>
If the machine is on a network, you can do:
make Experimental

This will send the results to the CMake dashboard.  Then others will be 
able to see the full results.  If not you can run ctest -V to see more 
verbose output.  If you can do the experimental, the results will be here:
http://public.kitware.com/dashboard.php?name=cmake

-Bill



-Bill



More information about the CMake mailing list