Re: parallel.c is not marked as test covered

Поиск
Список
Период
Сортировка
От Andres Freund
Тема Re: parallel.c is not marked as test covered
Дата
Msg-id 20160509145023.tkdpyygfxu56ngzz@alap3.anarazel.de
обсуждение исходный текст
Ответ на Re: parallel.c is not marked as test covered  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Ответы Re: parallel.c is not marked as test covered  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: parallel.c is not marked as test covered  (Clément Prévost <prevostclement@gmail.com>)
Re: parallel.c is not marked as test covered  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Список pgsql-hackers
On 2016-05-08 22:20:55 -0300, Alvaro Herrera 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 think it's a good idea to run a force-parallel run on some buildfarm
members. But I'm rather convinced that the core tests run by all animals
need some minimal coverage of parallel queries. Both because otherwise
it'll be hard to get some coverage of unusual platforms, and because
it's imo something rather relevant to test during development.

- Andres



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

Предыдущее
От: Euler Taveira
Дата:
Сообщение: Re: Patch for German translation
Следующее
От: Catalin Iacob
Дата:
Сообщение: Re: [COMMITTERS] pgsql: Add TAP tests for pg_dump