diff options
author | Thomas Rast <trast@inf.ethz.ch> | 2013-05-13 23:27:26 +0200 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2013-05-13 15:24:46 -0700 |
commit | dcbe7f1ab8b96b3875ae820d71c1364ee3bd99f5 (patch) | |
tree | dfc6a50312aa0e18d6ead647f2dde46ceeb62db1 /t/t9603 | |
parent | coverage: split build target into compile and test (diff) | |
download | tgif-dcbe7f1ab8b96b3875ae820d71c1364ee3bd99f5.tar.xz |
coverage: do not delete .gcno files before building
The coverage-compile target depends on coverage-clean, which is
supposed to remove the earlier build products that would get in the
way of the next coverage test run.
However, removing *.gcno is actively wrong. These are the files that
contain the compile-time coverage related data. They are only rebuilt
if the source is compiled. So if one ran 'make coverage' two times in
a row, the second run would remove *.gcno, but then fail to recreate
them because neither source files nor build flags have changed. (This
remained hidden for so long most likely because any other intervening
use of 'make' will change the build flags, causing a full rebuild.)
So we make an exception for *.gcno. The *.gcda are the coverage
results, written when the gcov-instrumented program is run. We still
remove those, so as to get a one-test-run view of the data; you could
probably argue the other way too.
Signed-off-by: Thomas Rast <trast@inf.ethz.ch>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t9603')
0 files changed, 0 insertions, 0 deletions