| From: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
|---|---|
| To: | Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Explicitly enable meson features in CI |
| Date: | 2025-07-10 17:12:05 |
| Message-ID: | CAOYmi+=0JUHJPBEnLWnhJ2pRxY-yjhx_mUaTo05xOfX9Xq=nsA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jul 10, 2025 at 2:59 AM Nazir Bilal Yavuz <byavuz81(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2025-07-10 17:31:56 | pg_dump sort priority mismatch for large objects |
| Previous Message | Tom Lane | 2025-07-10 17:05:54 | Adding some error context for lock wait failures |