From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: cirrus scripts could use make -k |
Date: | 2022-12-23 11:27:08 |
Message-ID: | 20221223112708.slcmbo3qqvgryv6v@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On 2022-12-15 12:31:26 +0100, Peter Eisentraut wrote:
> I would find it useful if the cirrus scripts used make -k (and ninja -k) to
> keep building everything in the presence of errors. For example, I once had
> some issue in code that caused a bunch of compiler warnings on Windows. The
> cirrus build would only show me the first one, then I had to fix, reupload,
> see the next one, etc. Are there any drawbacks to using these options in
> this context?
>
-1 - it makes it much harder to find the first error. To the point of
the error output getting big enough that CI task output gets deleted
more quickly because of the larger output.
I can see -k 3 or something though.
Greetings,
Andres Freund
From | Date | Subject | |
---|---|---|---|
Next Message | John Naylor | 2022-12-23 11:47:08 | Re: [PoC] Improve dead tuple storage for lazy vacuum |
Previous Message | Andres Freund | 2022-12-23 11:22:07 | Re: daitch_mokotoff module |