incorrect xlog.c coverage report

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема incorrect xlog.c coverage report
Дата
Msg-id 58ce1068-0cfc-3394-df69-ee0d03aaebb5@2ndquadrant.com
обсуждение исходный текст
Ответы Re: incorrect xlog.c coverage report
Список 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 по дате отправления:

Предыдущее
От: Amit Langote
Дата:
Сообщение: Re: ToDo: show size of partitioned table
Следующее
От: Kyotaro HORIGUCHI
Дата:
Сообщение: Re: pg_stat_ssl additions