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

From Henson Choi
Subject Re: Heads Up: cirrus-ci is shutting down June 1st
Date
Msg-id CAAAe_zBJMKLinHZvTb4kJxXxD_j+zgHzxsP8mc55GmRHS7vWqg@mail.gmail.com
Whole thread
In response to Re: Heads Up: cirrus-ci is shutting down June 1st  (Jacob Champion <jacob.champion@enterprisedb.com>)
Responses Re: Heads Up: cirrus-ci is shutting down June 1st
List pgsql-hackers
Hi,

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.

Regards,
Henson

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Handle concurrent drop when doing whole database vacuum
Next
From: Bharath Rupireddy
Date:
Subject: Re: Handle concurrent drop when doing whole database vacuum