Re: [HACKERS] make check-world output - Mailing list pgsql-hackers

From Jeff Janes
Subject Re: [HACKERS] make check-world output
Date
Msg-id CAMkU=1xt=+EbYEFwik9rHOHKYNVv7pqigG+ZApvF=kPctOLGig@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] make check-world output  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, Mar 10, 2017 at 6:19 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> Jeff Janes wrote:
>> There was some recent discussion about making "make check-world" faster.
>> I'm all for that, but how about making it quieter?  On both machines I've
>> run it on (CentOS6.8 and Ubuntu 16.04.2), it dumps some gibberish to
>> stderr, example attached.

> I think you're complaining about the test code added by commit
> fcd15f13581f.  Together with behavior introduced by 2f227656076a, it is
> certainly annoying.  I would vote for redirecting that output to a log
> file which can be ignored/removed unless there is a failure.

What about just reverting 2f227656076a?

That takes care of most of it, but leaves:

WARNING: enabling "trust" authentication for local connections
You can change this by editing pg_hba.conf or using the option -A, or
--auth-local and --auth-host, the next time you run initdb.
NOTICE:  database "regression" does not exist, skipping

Cheers,

Jeff

pgsql-hackers by date:

Previous
From: Jeff Janes
Date:
Subject: [HACKERS] Silence perl warning in check-world
Next
From: Andres Freund
Date:
Subject: Re: [HACKERS] [COMMITTERS] pgsql: Add amcheck extension to contrib.