Exclude flex-generated code from coverage testing
authorPeter Eisentraut <peter_e@gmx.net>
Fri, 11 Aug 2017 03:33:47 +0000 (23:33 -0400)
committerPeter Eisentraut <peter_e@gmx.net>
Mon, 16 Oct 2017 20:28:11 +0000 (16:28 -0400)
commit421167362242ce1fb46d6d720798787e7cd65aad
tree5f0c2620cd7364cd66404ca8a3433bb55d1291b3
parentcf5ba7c30c0428f5ff49197ec1e0f052035300d6
Exclude flex-generated code from coverage testing

Flex generates a lot of functions that are not actually used.  In order
to avoid coverage figures being ruined by that, mark up the part of the
.l files where the generated code appears by lcov exclusion markers.
That way, lcov will typically only reported on coverage for the .l file,
which is under our control, but not for the .c file.

Reviewed-by: Michael Paquier <michael.paquier@gmail.com>
12 files changed:
contrib/cube/cubescan.l
contrib/seg/segscan.l
src/backend/bootstrap/bootscanner.l
src/backend/parser/scan.l
src/backend/replication/repl_scanner.l
src/backend/replication/syncrep_scanner.l
src/backend/utils/misc/guc-file.l
src/bin/pgbench/exprscan.l
src/bin/psql/psqlscanslash.l
src/fe_utils/psqlscan.l
src/interfaces/ecpg/preproc/pgc.l
src/test/isolation/specscanner.l