Re: Extension coverage

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Gabriel Furstenheim Milerud <furstenheim(at)gmail(dot)com>
Cc: PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org>
Subject: Re: Extension coverage
Date: 2017-08-28 06:34:09
Message-ID: CAB7nPqTwtM-2xQZgrQV=_BFSP_8KHJQR75=Tpx2-ThcJcwEqpQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sat, Aug 26, 2017 at 6:28 PM, Gabriel Furstenheim Milerud
<furstenheim(at)gmail(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Moreno Andreo 2017-08-28 08:54:45 Re: [SPAM] Re: Invalid magic number 0000 in log file
Previous Message Michael Paquier 2017-08-28 06:05:14 Re: Retrieving query results