Re: Regression tests failures on Windows Server 2019 - on master at commit # d816f366b - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Regression tests failures on Windows Server 2019 - on master at commit # d816f366b
Date
Msg-id 20220304175735.nmfvg3khgb7xvmke@alap3.anarazel.de
Whole thread Raw
In response to Re: Regression tests failures on Windows Server 2019 - on master at commit # d816f366b  (Andres Freund <andres@anarazel.de>)
Responses Re: Regression tests failures on Windows Server 2019 - on master at commit # d816f366b  (Andres Freund <andres@anarazel.de>)
Re: Regression tests failures on Windows Server 2019 - on master at commit # d816f366b  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On 2022-03-04 09:46:44 -0800, Andres Freund wrote:
> On 2022-03-04 09:30:37 -0800, Andres Freund wrote:
> > I wonder if we're missing some steps, at least on windows, to make pg_ctl
> > start independent of the starting shell?
>
> Sure looks that way. On windows, if I do pg_ctl start, then hit ctrl-c, the
> server shuts down.

Short term the easiest fix might be to start postgres for those tests as a
service. But it seems we should fix whatever the cause of that
terminal-connectedness behaviour is.

I'm out for ~2-3h. I started a test run with using a service just now:
https://cirrus-ci.com/task/5519573792325632 but I very well might have typoed
something...



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Regression tests failures on Windows Server 2019 - on master at commit # d816f366b
Next
From: Andres Freund
Date:
Subject: Re: Regression tests failures on Windows Server 2019 - on master at commit # d816f366b