Re: Running make check-world in buildfarm (was Re: [COMMITTERS] pgsql: Use SASLprep to normalize passwords for SCRAM authentication.)
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: Michael Paquier <michael.paquier@gmail.com>, Andrew Dunstan <andrew@dunslane.net>
Cc: Heikki Linnakangas <hlinnaka@iki.fi>, Tom Lane <tgl@sss.pgh.pa.us>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2017-04-08T14:05:54Z
Lists: pgsql-hackers
On 2017-04-08 23:01:06 +0900, Michael Paquier wrote: > 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. I think it's partially knowing which target failed, and which regression.diffs to display. If we were able to revamp check-world so it outputs a list of targets the regression machinery were able to run individually, it'd probably help? - Andres
Commits
-
Fix the new SASLprep tests to work with non-UTF-8 locales.
- 9025af3ed039 10.0 landed
-
Use SASLprep to normalize passwords for SCRAM authentication.
- 60f11b87a234 10.0 cited