Thread

Re: Heads Up: cirrus-ci is shutting down June 1st

Nazir Bilal Yavuz <byavuz81@gmail.com> — 2026-05-25T12:14:41Z

Hi,

We had an unconference session at the PGConf.dev 2026. Here are the
notes [1] (Thank you Lukas for taking and publishing the notes!). Some
important points are:

- We can use Github Actions for now, and revisit alternatives later.
- We won't have BSDs for the first version.
- Backpatch until PG15, where CI introduced.
- No need to test VS 2019, we can continue with VS 2022.
- Deal with making logs public later.

On Tue, 19 May 2026 at 01:27, Nazir Bilal Yavuz <byavuz81@gmail.com> wrote:
>
> I think we can merge these two patches and move forward that way. I am
> planning to review your patch and see what I can come up with to get
> it to a committable state.

Here is the v2, I took Jelte's patch and reviewed & merged it with my
patch. Updates and questions are:

1- I continued to use Jelte's container method (Linux tasks only for
now, BSD tasks will be included in the future) because I think that is
the future-proof way since we might want to generate our container
images in the future. Also, up-to-date Debian images can be tested
with this way; otherwise we would need to use Ubuntu 24.04.

2- io_uring tests work on the Linux Meson task.

3- I didn't put commands to helper scripts for now. I think it is a
good thing to have a helper script but it would be better to have this
helper script after the first version is committed since it can extend
the timeline. Also, I found that having all commands in one file makes
debugging easier.

4- FreeBSD task has these options:

      PG_TEST_INITDB_EXTRA_OPTS: >-
        -c debug_copy_parse_plan_trees=on
        -c debug_write_read_parse_plan_trees=on
        -c debug_raw_expression_coverage_test=on
        -c debug_parallel_query=regress

Since we won't have FreeBSD for the first version. I put these options
to the MacOS task but I couldn't decide where to put
'PG_TEST_PG_UPGRADE_MODE: --link'.

Also, I am planning to work on back patches when we agree on the
upstream one. Does that sound good?

CI run link of attached patch:
https://github.com/nbyavuz/postgres/actions/runs/26398508250

[1] https://wiki.postgresql.org/wiki/PGConf.dev_2026_Developer_Unconference

-- 
Regards,
Nazir Bilal Yavuz
Microsoft