From: Tom Lane <tgl@sss.pgh.pa.us>
To: Noah Misch <noah@leadboat.com>
cc: buildfarm-members@lists.postgresql.org
Subject: Re: Animals with old SSL may find no build required
In-reply-to: <20211002070010.GB205991@rfd.leadboat.com>
References: <20211002070010.GB205991@rfd.leadboat.com>
Comments: In-reply-to Noah Misch <noah@leadboat.com>
	message dated "Sat, 02 Oct 2021 00:00:10 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3689081.1633185948.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Sat, 02 Oct 2021 10:45:48 -0400
Message-ID: <3689082.1633185948@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/3689082.1633185948%40sss.pgh.pa.us>
Precedence: bulk

Noah Misch <noah@leadboat.com> writes:
> build-farm.conf.sample defaults to git_ignore_mirror_failure=3D>1.  With=
 that
> setting, if a buildfarm member SSL setup breaks, the member will appear =
to be
> functioning, but it will find no changes to test:

> Sat Oct  2 04:35:22 2021: buildfarm run for frogfish:REL9_6_STABLE start=
ing
> git version 1.7.10.4 too old for automatic default branch update
> frogfish:REL9_6_STABLE [04:35:23] checking out source ...
> frogfish:REL9_6_STABLE [04:35:58] checking if build run needed ...
> frogfish:REL9_6_STABLE [04:35:58] No build required: last status =3D Fri=
 Sep 24 23:15:14 2021 GMT, current snapshot =3D Sat Sep 25 14:53:55 2021 G=
MT, changed files =3D 0

FWIW, if you are using run_branches.pl, the failure will happen earlier.
What I am getting on prairiedog is

error getting branches of interest: 500 Can't connect to buildfarm.postgre=
sql.org:443 (certificate verify failed) at ./run_branches.pl line 201.

I worked around it for the moment by s/https/http/g in the config file,
but I'm hoping to find where the obsolete trust store is and update it.
(I thought updating perl's Mozilla::CA would do the trick, but nope.)

			regards, tom lane