Re: ci: Allow running mingw tests by default via environment variable

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, Wolfgang Walther <walther(at)technowledgy(dot)de>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Tomas Vondra <tomas(at)vondra(dot)me>
Subject: Re: ci: Allow running mingw tests by default via environment variable
Date: 2025-04-14 19:22:40
Message-ID: Z_1ggHleUAdcZx7Y@nathan
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Apr 12, 2025 at 08:18:35PM +1200, Thomas Munro wrote:
> Is it safe to assume that CI changes come under the same code-freeze
> exception as tests and docs? I would assume so, it's just scripting
> glue in .cirrus.XXX files not affecting one bit of the software, but I
> don't recall that we specifically clarified that before, so can
> someone from the RMT please +1 this? Then I'll go ahead and push
> these.

That seems reasonable to me. But to play devil's advocate, is there a
strong reason for doing this before July?

--
nathan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2025-04-14 19:26:59 Re: ci: Allow running mingw tests by default via environment variable
Previous Message Jacob Champion 2025-04-14 19:14:20 Re: [PoC] Federated Authn/z with OAUTHBEARER