Message-ID: <aee3de02-1e5d-ae0a-c3e7-23cb1ef8cd70@dunslane.net>
Date: Sat, 26 Mar 2022 16:57:39 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.5.0
Subject: Re: Why is lorikeet so unstable in v14 branch only?
Content-Language: en-US
To: Andres Freund <andres@anarazel.de>, Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@lists.postgresql.org
References: <136102.1648320427@sss.pgh.pa.us>
 <20220326194948.mksfw6z3fysojpxx@alap3.anarazel.de>
From: Andrew Dunstan <andrew@dunslane.net>
In-Reply-To: <20220326194948.mksfw6z3fysojpxx@alap3.anarazel.de>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/aee3de02-1e5d-ae0a-c3e7-23cb1ef8cd70%40dunslane.net>
Precedence: bulk


On 3/26/22 15:49, Andres Freund wrote:
> On 2022-03-26 14:47:07 -0400, Tom Lane wrote:
>> I chanced to notice that buildfarm member lorikeet has been
>> failing an awful lot lately in the v14 branch, but hardly
>> at all in other branches.  Here's a log extract from its
>> latest run [1]:
> One interesting bit in the config is:
>
>                    'extra_config' => {
>                    ...
>                                        'HEAD' => [
>                                                    'update_process_title = off'
>                                                  ],
>                                        'REL_13_STABLE' => [
>                                                             'update_process_title = off'
>                                                           ]
>

I'd forgotten about that. Let me do that for REL_14_STABLE and see where
we get to.


>> *** starting debugger for pid 53762, tid 10536
>> 2022-03-26 06:32:02.158 EDT [623eeb6c.d0c2:4] LOG:  server process (PID 53762) exited with exit code 127
>> 2022-03-26 06:32:02.158 EDT [623eeb6c.d0c2:5] DETAIL:  Failed process was running: create table mlparted_tab_part1 partition of mlparted_tab for values in (1);
>> 2022-03-26 06:32:02.158 EDT [623eeb6c.d0c2:6] LOG:  terminating any other active server processes
> I wonder what where the output of "starting debugger for pid 53762" ends up? I
> assume it's triggered by
>                                     'CYGWIN' => 'server error_start=c:\\ncygwin64\\bin\\dumper.exe -d %1 %2',
>
> https://cygwin.org/cygwin-ug-net/using-cygwinenv.html
> says "The filename of the executing program and it's Windows process id are appended to the command as arguments. "
>
> but nothing about %1 and %2 :(. I those are just "executing program" and
> "Windows process id" respectively?


I don't remember where I got this invocation from. But see for example
<https://stackoverflow.com/questions/320001/using-a-stackdump-from-cygwin-executable>


cheers


andrew


--
Andrew Dunstan
EDB: https://www.enterprisedb.com