| From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
|---|---|
| To: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com> |
| Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Probable CF bot degradation |
| Date: | 2022-03-20 13:28:38 |
| Message-ID: | 20220320132838.2zdnpu6vcravpbs2@jrouhaud |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Mar 20, 2022 at 01:58:01PM +0100, Matthias van de Meent wrote:
>
> I noticed that two of my patches (37/3543 and 37/3542) both failed due
> to a bad commit on master (076f4d9). The issue was fixed an hour later
> with b61e6214; but the pipeline for these patches hasn't run since.
> Because doing a no-op update would only clutter people's inboxes, I
> was waiting for CFBot to do its regular bitrot check; but that hasn't
> happened yet after 4 days.
> I understand that this is probably due to the high rate of new patch
> revisions that get priority in the queue; but that doesn't quite
> fulfill my want for information in this case.
Just in case, if you only want to know whether the cfbot would be happy with
your patches you can run the exact same checks using a personal github repo, as
documented at src/tools/ci/README.
You could also send the URL of a successful run on the related threads, or as
an annotation on the cf entries to let possible reviewers know that the patch
is still in a good shape even if the cfbot is currently still broken.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2022-03-20 13:34:50 | Re: A test for replay of regression tests |
| Previous Message | Matthias van de Meent | 2022-03-20 12:58:01 | Re: Probable CF bot degradation |