Re: [HACKERS] Running make check-world in buildfarm (was Re:[COMMITTERS] pgsql: Use SASLprep to normalize passwords for SCRAM authentication.) - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: [HACKERS] Running make check-world in buildfarm (was Re:[COMMITTERS] pgsql: Use SASLprep to normalize passwords for SCRAM authentication.)
Date
Msg-id CAB7nPqRqC=8SaNqpc3H7AF_GrY2pa=C7C8SMvmi4f6VNT4JFQA@mail.gmail.com
Whole thread Raw
In response to [HACKERS] Running make check-world in buildfarm (was Re: [COMMITTERS] pgsql:Use SASLprep to normalize passwords for SCRAM authentication.)  (Heikki Linnakangas <hlinnaka@iki.fi>)
Responses Re: [HACKERS] Running make check-world in buildfarm (was Re:[COMMITTERS] pgsql: Use SASLprep to normalize passwords for SCRAMauthentication.)  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Sat, Apr 8, 2017 at 7:33 PM, Heikki Linnakangas <hlinnaka@iki.fi> wrote:
> Hmm. It looks like none of the buildfarm members are running the
> authentication tests. Nor recovery tests, nor subscription tests. We're
> missing a trick here, at least some of the buildfarm members really ought to
> run "make check-world", we're missing a lot of coverage otherwise.

I recall that Andrew has been favoring as much as possible one folder
path per test series in the buildfarm client (perhaps to keep the
tests separated and have the logs easier to analyze?). I would not
mind much if this is replaced by a pure make check-world, which is
what most of the serious hackers do, or at least a make check running
from src/test to save us a lot of maintenance pain.
-- 
Michael



pgsql-hackers by date:

Previous
From: David Steele
Date:
Subject: Re: [HACKERS] postgres_fdw bug in 9.6
Next
From: David Steele
Date:
Subject: Re: [HACKERS] WIP: Covering + unique indexes.