| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Cc: | Robert Haas <rhaas(at)postgresql(dot)org>, Alexander Korotkov <akorotkov(at)postgresql(dot)org> |
| Subject: | Re: buildfarm warnings |
| Date: | 2022-02-14 20:11:52 |
| Message-ID: | 5c3b412d-ca28-a0d1-6aab-ef95b43d08fd@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2/12/22 16:13, Justin Pryzby wrote:
> Is there any check for warnings from new code, other than those buildfarm
> members with -Werror ?
I had forgotten about this :-) but a few years ago I provided a
check_warnings setting (and a --check-warnings command line parameter).
It's processed if set in the main build steps ("make", "make contrib"
and "make_test_modules") as well as some modules that check external
software. But it hasn't been widely advertised so it's probably in
hardly any use, if at all.
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2022-02-14 20:15:14 | Observability in Postgres |
| Previous Message | Robert Haas | 2022-02-14 20:07:46 | Re: Teach pg_receivewal to use lz4 compression |