Re: Explicitly enable meson features in CI - Mailing list pgsql-hackers

From Jacob Champion
Subject Re: Explicitly enable meson features in CI
Date
Msg-id CAOYmi+=0JUHJPBEnLWnhJ2pRxY-yjhx_mUaTo05xOfX9Xq=nsA@mail.gmail.com
Whole thread Raw
In response to Re: Explicitly enable meson features in CI  (Nazir Bilal Yavuz <byavuz81@gmail.com>)
Responses Re: Explicitly enable meson features in CI
List pgsql-hackers
On Thu, Jul 10, 2025 at 2:59 AM Nazir Bilal Yavuz <byavuz81@gmail.com> wrote:
> Andres off-list mentioned that if we explicitly enable features for
> *all* of the tasks, then none of the tasks will be testing the auto
> feature option and I agree with Andres. My suggestion is setting
> features to auto for Debian - Meson task. I decided on this because I
> think it is the most checked CI task

Hehe, that's certainly true for me...

> so it would be easier to catch if
> one of the features is disabled without anyone noticing.

Seems reasonable. If we do this, can we rename the job with a "- Meson
Auto" suffix or something, to try to call the difference out
explicitly?

--Jacob



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Adding some error context for lock wait failures
Next
From: Nathan Bossart
Date:
Subject: pg_dump sort priority mismatch for large objects