| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Lukas Fittl <lukas(at)fittl(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Broken ./configure checks for __cpuid() and __cpuidex() |
| Date: | 2025-08-08 21:23:13 |
| Message-ID: | t6o7635yhv42ilikutrtrvzpcn7u3tbaf7hovnjikzv57e6xxx@ayxchpgzxodj |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2025-07-29 00:21:32 -0700, Lukas Fittl wrote:
> On Mon, Jul 28, 2025 at 10:30 PM Michael Paquier <michael(at)paquier(dot)xyz>
> wrote:
> > > I'm not sure how to get CI to run MinGW (it appears paused for me?), so I
> > > can't test this myself easily.
> >
> > src/tools/ci/README, "Enabling cirrus-ci in a github repository".
> > I've enabled it in my own copy of Postgres on github, relying on that
> > as an extra pre-commit check mostly for patches that are OS-sensitive.
> > It runs independently on the CI, relying on the OS base images that
> > Andres has been cooking for the last few years, of course.
> >
>
> Thanks, to be clear, I have CI enabled but the MinGW tasks were always
> paused (presumably because of the trigger type being manual). But I think
> "ci-os-only" as noted in the README should do the trick, I'll go
> investigate that.
FWIW, you can trigger manual tasks in the cirrus-ci web-interface.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jacob Champion | 2025-08-08 21:31:49 | Re: [PATCH] OAuth: fix performance bug with stuck multiplexer events |
| Previous Message | Dagfinn Ilmari Mannsåker | 2025-08-08 21:16:22 | Re: [PATCH] OAuth: fix performance bug with stuck multiplexer events |