Re: Heads Up: cirrus-ci is shutting down June 1st - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: Heads Up: cirrus-ci is shutting down June 1st
Date
Msg-id CA+hUKGKz2mFkQpmzvne0G0Ht7=-MSAbds2cfTkon6dyc1k=R-w@mail.gmail.com
Whole thread
In response to Re: Heads Up: cirrus-ci is shutting down June 1st  (Henson Choi <assam258@gmail.com>)
List pgsql-hackers
On Mon, Jun 29, 2026 at 12:26 PM Henson Choi <assam258@gmail.com> wrote:
> Since cfbot keeps coming up here, a quick bug report.
>
> cfbot treats a .tgz attachment as a patch even when the archive has no
> patch inside.  It then applies nothing, tests plain master, and reports
> green -- so a real patch posted earlier drops out of testing and the CF
> entry shows a false green.
>
> Live example: CF 5802 (Unicode Normalization).  The last real patchset
> is v11.  My next message attached coverage.tgz (a gcov HTML report, not
> a patch); cfbot took that as the latest submission and has been testing
> master ever since.  That's the reproducer -- and the reason 5802 looks
> "stale/merged" on the dashboard when it isn't.
>
> Suggested fix: only treat an attachment as a patch if it's a
> .patch/.diff, or an archive containing one; otherwise ignore it and fall
> back to the last attachment set that had patches.

Ack.  I will try to improve this...



pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: In core use of RegisterXactCallback() and RegisterSubXactCallback()
Next
From: Michael Paquier
Date:
Subject: Re: [PATCH] Change wait_time column of pg_stat_lock to double precision