Re: Update Windows CI Task Names: Server 2022 + VS 2022 Upgrade

From: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
To: Peter Eisentraut <peter(at)eisentraut(dot)org>
Cc: Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>
Subject: Re: Update Windows CI Task Names: Server 2022 + VS 2022 Upgrade
Date: 2025-09-11 14:55:37
Message-ID: CAOYmi+=iuJWZqFQm-NM-extwD9ipNRq4Q0CkxMcktMDS+WKbJg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Sep 11, 2025 at 7:18 AM Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:
> I don't think we need this level of complication. We already have the
> situation that for example "linux" covers several tasks

Recently, I've wished that it were otherwise; if I'm debugging a
Meson-only test failure in Linux, I don't want to burn credits running
Autoconf.

> and "windows"
> also covers several tasks, one of which is manually triggered.

I think it only covers one? The other is `mingw` (and I've used that
one recently, for the pytest work).

--Jacob

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kirill Reshke 2025-09-11 15:00:03 Re: ALTER DATABASE RESET with unexistent guc doesn't report an error
Previous Message Robert Haas 2025-09-11 14:52:14 Re: Extension security improvement: Add support for extensions with an owned schema