incorrect xlog.c coverage report - Mailing list pgsql-hackers

From Peter Eisentraut
Subject incorrect xlog.c coverage report
Date
Msg-id 58ce1068-0cfc-3394-df69-ee0d03aaebb5@2ndquadrant.com
Whole thread Raw
Responses Re: incorrect xlog.c coverage report  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
I noticed some strangeness in the test coverage reporting.  For example,
in
https://coverage.postgresql.org/src/backend/access/transam/xlog.c.gcov.html
in the function readRecoveryCommandFile(), most of the branches parsing
the individual recovery options (recovery_target_xid,
recovery_target_time, etc.) are shown as never hit, even though there
are explicit tests for this in
src/test/recovery/t/003_recovery_targets.pl.  I tried this locally and
also with -O0 just in case, but I get the same results.  Any ideas?

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: ToDo: show size of partitioned table
Next
From: Kyotaro HORIGUCHI
Date:
Subject: Re: pg_stat_ssl additions