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

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: assam258(at)gmail(dot)com
Cc: Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>, Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>, pgsql-hackers(at)postgresql(dot)org, Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
Subject: Re: Heads Up: cirrus-ci is shutting down June 1st
Date: 2026-06-29 01:54:04
Message-ID: CA+hUKGKz2mFkQpmzvne0G0Ht7=-MSAbds2cfTkon6dyc1k=R-w@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jun 29, 2026 at 12:26 PM Henson Choi <assam258(at)gmail(dot)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...

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2026-06-29 02:11:06 Re: [PATCH] Change wait_time column of pg_stat_lock to double precision
Previous Message Amit Langote 2026-06-29 01:26:33 Re: In core use of RegisterXactCallback() and RegisterSubXactCallback()