[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [rcs] restrict coverage analysis to src/, tests/

From: Thien-Thi Nguyen
Subject: Re: [rcs] restrict coverage analysis to src/, tests/
Date: Mon, 31 Jan 2011 14:12:11 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux)

() address@hidden (Ludovic Courtès)
() Mon, 31 Jan 2011 13:32:33 +0100

   Test coverage roughly consists in running ‘make && make check’ with
   ‘CFLAGS=--coverage LDFLAGS=--coverage’.  Restricting it would require
   inconvenient hacks, I think, and wouldn’t save CPU cycles.

Doing less work surely would save some cycles.  However, if it's inconvenient,
that's another question...

Unfortunately the nixpkgs-manual.html i have locally is at "draft (version
0.14)" and does not even mention the "coverage" phase, else i'd take a look
at what's involved.  I see from the output:

          ☆ Scanning . for .gcda files ...
          ☆ Found 45 data files in .
          ☆ Processing src/rcstime.gcda
          ☆ Processing src/rcsgen.gcda
          ☆ Processing src/rcsmap.gcda                                          
          ☆ Processing src/b-fro.gcda                                           
          ☆ Processing tests/btdt.gcda                                          
          ☆ Processing lib/fcntl.gcda                                           
          ☆ Processing lib/xalloc-die.gcda                                      
          ☆ Finished .info-file creation                                        
          ☆ Reading tracefile app.info                                          
          ☆ Overall coverage rate:                                              

so i guess the overall approach would be to change the one scan into two,
specifying both resulting tracefiles instead of the monolithic app.info.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]