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

Hi,

On Sat, 13 Jun 2026 at 00:54, Andres Freund <andres@anarazel.de> wrote:
>
> > > - I comparison to cirrus-ci it's considerably more painful (and it wasn't
> > >   exactly pain-free on cirrus either) to access the logs of failed tasks. One
> > >   can't just link to the failure or such.
> > >
> > >   I have wondered about determining which test failed first, and uploading the
> > >   most crucial logs for that test separately, so one could at least look and
> > >   link to those without unpacking a .zip.
> >
> > I have questions about this. If we do this for all jobs then we can
> > end up having just too many uploaded files to look at. In this case,
> > unpacking .zip would be easier to access the logs of failed tasks.
>
> I was thinking we'd do this only for the first failure...

I assume you mean first failure for the GHA run, not the first failure
per GHA job. Then, this makes sense. I just wonder how this can be
implemented.


I have only one comment on v13a-0002, I looked at the rest and all LGTM.

Subject: [PATCH v13a 2/9] ci: Use meson for most of CompilerWarnings, it's a
 lot faster

meson_common_features and linux_configure_features are not the same.
By using meson_common_features, we don't test:

    --with-gssapi
    --with-libcurl
    --with-llvm
    --with-pam
    --with-selinux
    --with-systemd
    --with-uuid=ossp

options. Is this a problem?


--
Regards,
Nazir Bilal Yavuz
Microsoft