Horton

Re: buildfarm warnings

Andrew Dunstan <andrew@dunslane.net>

View thread View on postgr.es
From: Andrew Dunstan <andrew@dunslane.net>
To: Justin Pryzby <pryzby@telsasoft.com>, pgsql-hackers@postgresql.org
Cc: Robert Haas <rhaas@postgresql.org>, Alexander Korotkov <akorotkov@postgresql.org>
Date: 2022-02-14T20:11:52Z
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

Commits

  1. Avoid dangling-pointer usage in pg_basebackup progress reports.

  2. Delete contrib/xml2's legacy implementation of xml_is_well_formed().