Fwd: [CMake] CMake 2.8.0 RC 4 ready for testing!

[Brad King]

David Faure wrote:
> On Thursday 29 October 2009, Alexander Neundorf wrote:
>> Hi,
>>
>> please give this RC4 of CMake 2.8.0 try, it is getting close to the final
>> 2.8.0.
> 
> OK, I switched to CMake-2-8 cvs branch today.
> Everything seems to go smoothly, no problems.

Great, thanks for trying it.

> Just one cosmetic remark: why does the output of `make test` now look like 
> this?
> 
>       Start  1: klocaletest                                                                                                           
>  1/46 Test  #1: klocaletest ......................   Passed    0.08 sec                                                               
>       Start  2: klocalizedstringtest                                                                                                  
>  2/46 Test  #2: klocalizedstringtest .............   Passed    0.03 sec                                                               
>       Start  3: kstandarddirstest                                                                                                     
>  3/46 Test  #3: kstandarddirstest ................   Passed    0.09 sec                                                               
>       Start  4: kaboutdatatest                                                                                                        
>  4/46 Test  #4: kaboutdatatest ...................   Passed    0.02 sec                                                               
>       Start  5: kurltest                                                                                                              
>  5/46 Test  #5: kurltest .........................***Failed    0.03 sec  
> [...]
> 
> I think this makes it harder to read (twice longer, with one line out of two
> saying nothing really interesting; the "Start N: footest" line seems useless).

This is because we now support parallel testing: ctest -j 8

The problem is that we do not know the order in which tests will
start or end.  No partial lines can be printed.  Originally we
just printed output only when tests ended.  However, that leaves
no indication of what tests are currently running.  If the first
tests are long, there is no indication anything happens.

In the future, we plan to solve this problem by detecting whether
the output pipe is a tty.  If not, then we can just write the
ending lines and no start lines.  If it is a tty then we can use
escape sequences to keep pending tests listed on the bottom as
each test finishes and a new one starts.  All of this requires
quite a bit of work to do cross-platform, so for now we just went
with the starting lines.  We purposely arranged the columns so
that the most important information on the ending lines sticks
out.

-Brad