Re: backup manifests and contemporaneous buildfarm failures
От | Andrew Dunstan |
---|---|
Тема | Re: backup manifests and contemporaneous buildfarm failures |
Дата | |
Msg-id | CAA8=A7-FFbnpVGg5-T-tvNLhLN_XkD6yGpJ9VHKqsROiHnsFFw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: backup manifests and contemporaneous buildfarm failures (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: backup manifests and contemporaneous buildfarm failures
|
Список | pgsql-hackers |
On Tue, Apr 7, 2020 at 12:37 AM Tom Lane <tgl@sss.pgh.pa.us> wrote: > > Robert Haas <robertmhaas@gmail.com> writes: > > Taking stock of the situation this morning, most of the buildfarm is > > now green. There are three failures, on eelpout (6 hours ago), > > fairywren (17 hours ago), and hyrax (3 days, 7 hours ago). > > fairywren has now done this twice in the pg_validatebackupCheck step: > > exec failed: Bad address at /home/pgrunner/bf/root/HEAD/pgsql.build/../pgsql/src/test/perl/TestLib.pm line 340. > at /home/pgrunner/bf/root/HEAD/pgsql.build/../pgsql/src/test/perl/TestLib.pm line 340. > > I'm a tad suspicious that it needs another perl2host() > somewhere, but the log isn't very clear as to where. > > More generally, I wonder if we ought to be trying to > centralize those perl2host() calls instead of sticking > them into individual test cases. > > Not sure about that. I'll see if I can run it by hand and get some more info. What's quite odd is that jacana (a very similar setup) is passing this happily. cheers andrew -- Andrew Dunstan https://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: