Message-ID: <5c3b412d-ca28-a0d1-6aab-ef95b43d08fd@dunslane.net>
Date: Mon, 14 Feb 2022 15:11:52 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.5.0
Subject: Re: buildfarm warnings
Content-Language: en-US
To: Justin Pryzby <pryzby@telsasoft.com>, pgsql-hackers@postgresql.org
Cc: Robert Haas <rhaas@postgresql.org>,
 Alexander Korotkov <akorotkov@postgresql.org>
References: <20220212211316.GK31460@telsasoft.com>
From: Andrew Dunstan <andrew@dunslane.net>
In-Reply-To: <20220212211316.GK31460@telsasoft.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://www.postgresql.org/message-id/5c3b412d-ca28-a0d1-6aab-ef95b43d08fd%40dunslane.net>
Precedence: bulk


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