| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: make check-world output |
| Date: | 2017-03-11 03:06:20 |
| Message-ID: | c28ac440-d384-6102-571c-6eeadc0c98a5@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mengxing Liu | 2017-03-11 03:12:05 | [GSOC 17] Eliminate O(N^2) scaling from rw-conflict tracking in serializable transactions |
| Previous Message | Tom Lane | 2017-03-11 02:19:25 | Re: make check-world output |