Re: Regression tests failures on Windows Server 2019 - on master at commit # d816f366b

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Regression tests failures on Windows Server 2019 - on master at commit # d816f366b
Date: 2022-03-04 17:57:35
Message-ID: 20220304175735.nmfvg3khgb7xvmke@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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...

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2022-03-04 18:10:24 Re: Regression tests failures on Windows Server 2019 - on master at commit # d816f366b
Previous Message Andres Freund 2022-03-04 17:46:44 Re: Regression tests failures on Windows Server 2019 - on master at commit # d816f366b