Re: [GENERAL] Extension coverage

Поиск
Список
Период
Сортировка
От Gabriel Furstenheim Milerud
Тема Re: [GENERAL] Extension coverage
Дата
Msg-id CAJN3DWrmeoH10mrHWm98sPqMCmC-fP61jC7pkFN7gY7XxpFm0Q@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [GENERAL] Extension coverage  (Michael Paquier <michael.paquier@gmail.com>)
Список pgsql-general
Great thanks, didn't realize that I was already importing coverage from pgxs.

BTW, it fixed itself alone. At some point it started creating the .gcda files and making the target.

On 28 August 2017 at 08:34, Michael Paquier <michael.paquier@gmail.com> wrote:
On Sat, Aug 26, 2017 at 6:28 PM, Gabriel Furstenheim Milerud
<furstenheim@gmail.com> wrote:
> Not sure I follow. Do you have an example that I could check?
> I have the impression that my problem is that no .gcda files are created. If
> I just run the lcov part:
>     lcov -d . -c -o lcov.info
>
> I get
>    Found gcov version: 5.4.0
>    Scanning . for .gcda files ...
>    geninfo: WARNING: no .gcda files found in . - skipping!
>    Finished .info-file creation
>
> and an empty file lcov.info is created.
>
> Just to check, I've tried running make coverage and make coverage-html on
> the folder of postgres instead of the extension and that works.

There is no need to complicate your Makefile with a custom coverage
target, which is, at least it seems to me, the origin of the problems
you are seeing here. So you could just use the one that Postgres' PGXS
provides. Here is a simple Makefile I have used for coverage testing
with an extension:
https://github.com/michaelpq/pg_plugins/blob/master/decoder_raw/Makefile
If you enforce abs_top_srcdir=$(pwd) with make coverage, or
coverage-html if you want, then both are able to work properly. At
least for me they do.
--
Michael

В списке pgsql-general по дате отправления:

Предыдущее
От: Stephen Frost
Дата:
Сообщение: Re: [GENERAL] Logging the fact that a log was shipped
Следующее
От: Jeff Janes
Дата:
Сообщение: Re: [GENERAL] Performance with high correlation in group by on PK