| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-05 04:06:43 |
| Message-ID: | 20220305040643.njuzrfbagk7ck3pm@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2022-03-05 16:39:21 +1300, Thomas Munro wrote:
> On Sat, Mar 5, 2022 at 4:19 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> > https://github.com/cirruslabs/cirrus-ci-agent/issues/218#issuecomment-1059657781
>
> Oof. Nice detective work.
Thanks.
> > As indicated in the message above it, there's a workaround. Not sure if worth
> > committing, if they were to fix it in a few days? cfbot could be repaired by
> > just adding a repo environment variable of CIRRUS_AGENT_VERSION 1.73.2...
> > OTOH, committing and reverting a single line + comment is cheap.
>
> I vote for committing that workaround into the tree temporarily,
> because it's not just cfbot, it's also everyone's dev branches on
> Github + the official mirror that are red.
I'll do so after making dinner, unless you want to do so sooner. It did fix
the problem (intermixed with a few irrelevant changes): https://cirrus-ci.com/task/4928987829895168
- Andres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2022-03-05 06:01:22 | Re: Regression tests failures on Windows Server 2019 - on master at commit # d816f366b |
| Previous Message | Thomas Munro | 2022-03-05 03:39:21 | Re: Regression tests failures on Windows Server 2019 - on master at commit # d816f366b |