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

From Peter Eisentraut
Subject Re: [HACKERS] make check-world output
Date
Msg-id c28ac440-d384-6102-571c-6eeadc0c98a5@2ndquadrant.com
Whole thread Raw
In response to Re: [HACKERS] make check-world output  (Jeff Janes <jeff.janes@gmail.com>)
List pgsql-hackers
On 3/10/17 19:26, Jeff Janes wrote:
>     and there will be an exit code.
> 
> 
> True.  But I generally don't rely on that, unless the docs explicitly
> tell me to.
> 
> 
>     If we show no output, then other people will complain that they can't
>     tell whether it's hanging.
> 
> 
> Isn't that what stdout is for?

I haven't ever looked at the difference between stdout and stderr output
from the build process.  I rely on the exit code to tell me what
happened.  I don't mind changing things if it helps.

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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] make check-world output
Next
From: "Mengxing Liu"
Date:
Subject: [HACKERS] [GSOC 17] Eliminate O(N^2) scaling from rw-conflict tracking inserializable transactions