| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: The xversion-upgrade test fails to stop server |
| Date: | 2024-06-08 20:35:24 |
| Message-ID: | 94a0e4ac-0fab-467e-999c-0f6e16452ed0@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2024-06-08 Sa 10:00, Alexander Lakhin wrote:
> Hello,
>
> 30.05.2024 18:00, Alexander Lakhin wrote:
>> While reviewing recent buildfarm failures, I came across this one:
>> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2024-05-23%2004%3A11%3A03
>>
>>
>> upgrade.crake/REL_16_STABLE/REL9_5_STABLE-ctl4.log
>> waiting for server to shut
>> down...........................................................................................................................
>> failed
>> pg_ctl: server does not shut down
>>
>
> I've grepped through logs of the last 167
> xversion-upgrade-REL9_5_STABLE-REL_16_STABLE/*ctl4.log on crake and got
> the following results:
> waiting for server to shut down........ done
>
[...]
>
> So maybe it would make sense to increase default PGCTLTIMEOUT for
> buildfarm clients, say, to 180 seconds?
Sure. For now I have added it to the config on crake, but we can make it
a default.
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2024-06-08 20:40:28 | Re: Windows: openssl & gssapi dislike each other |
| Previous Message | Tom Lane | 2024-06-08 20:04:35 | Re: cannot drop intarray extension |