Re: parallel.c is not marked as test covered - Mailing list pgsql-hackers

From David Rowley
Subject Re: parallel.c is not marked as test covered
Date
Msg-id CAKJS1f8XBC1Qy2rguCZ3f1RG12y4s6sgjuhFWA08uFTNQJEN4g@mail.gmail.com
Whole thread Raw
In response to Re: parallel.c is not marked as test covered  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: parallel.c is not marked as test covered  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On 9 May 2016 at 13:20, Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
> David Rowley wrote:
>
>> I'm not entirely sure which machine generates that coverage output,
>> but the problem with it is that it's just one machine. We do have at
>> least one buildfarm member which runs with force_parallel_mode =
>> regress.
>
> It's not a buildfarm machine, but a machine setup specifically for
> coverage reports.  It runs "make check-world" only.  I can add some
> additional command(s) to run, if somebody can suggest something.

I'm not familiar with what's possible with make check-world, but would
it be reasonable to make that just do another regression test run with
force_parallel_mode set to regress?

-- David Rowley                   http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: Stopping logical replication protocol
Next
From: "David G. Johnston"
Date:
Subject: Re: First-draft release notes for next week's back-branch releases