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

From Peter Eisentraut
Subject Re: parallel.c is not marked as test covered
Date
Msg-id 48de8ea0-ae7c-d3e9-6c98-cb6b77d85708@2ndquadrant.com
Whole thread Raw
In response to Re: parallel.c is not marked as test covered  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: parallel.c is not marked as test covered  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
On 6/20/16 11:16 PM, Tom Lane wrote:
>> > I think this test would only fail if it runs out of workers, and that
>> > would only happen in an installcheck run against a server configured in
>> > a nonstandard way or that is doing something else -- which doesn't
>> > happen on the buildfarm.
> Um, if you're speaking of select_parallel, that already runs in parallel
> with two other regression tests, and there is no annotation in the
> parallel_schedule file suggesting that adding more scripts to that group
> would be bad.  But yes, perhaps putting this test into its own standalone
> group would be enough of a fix.

Maybe now would be a good time to address this by applying the attached
patch to master and seeing what happens?

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

Attachment

pgsql-hackers by date:

Previous
From: Dmitry Igrishin
Date:
Subject: Re: [GENERAL] C++ port of Postgres
Next
From: Jim Nasby
Date:
Subject: Re: [GENERAL] C++ port of Postgres