From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Noah Misch <noah(at)leadboat(dot)com> |
Cc: | buildfarm-members(at)lists(dot)postgresql(dot)org |
Subject: | Re: Animals with old SSL may find no build required |
Date: | 2021-10-02 14:45:48 |
Message-ID: | 3689082.1633185948@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | buildfarm-members |
Noah Misch <noah(at)leadboat(dot)com> writes:
> build-farm.conf.sample defaults to git_ignore_mirror_failure=>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 starting
> 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 = Fri Sep 24 23:15:14 2021 GMT, current snapshot = Sat Sep 25 14:53:55 2021 GMT, changed files = 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.postgresql.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
From | Date | Subject | |
---|---|---|---|
Next Message | Noah Misch | 2021-10-02 16:19:26 | Re: Animals with old SSL may find no build required |
Previous Message | Noah Misch | 2021-10-02 07:00:10 | Animals with old SSL may find no build required |