Re: cfbot mistakenly reports that a rebase is needed - Mailing list pgsql-hackers

From Aleksander Alekseev
Subject Re: cfbot mistakenly reports that a rebase is needed
Date
Msg-id CAJ7c6TMx9PvSTbsgNjmRoYcJ+DU5TyCJz50ygDEBTVwqOSaR=g@mail.gmail.com
Whole thread Raw
In response to Re: cfbot mistakenly reports that a rebase is needed  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: cfbot mistakenly reports that a rebase is needed
List pgsql-hackers
Hi,

> > Isn't the cfbot.cputube.org web page obsolete now that we have the CI
> > status directly in the commitfest page?
>
> Well, yeah, it's kind of duplicative --- but it slices the data
> differently and it presents it differently.  The more modern
> pages don't have an easily-bookmarked summary of the state of
> your own patches.  (The "dashboard" page is cluttered with a ton
> of other stuff, or at least it is for me.)  So I still use the
> cputube.org pages often, and I guess Aleksander does too.

cfbot is more convenient in my typical use cases.

Let's say I want to check if any of my patches needs a rebase. I just open:

https://cfbot.cputube.org/aleksander-alekseev.html

... and instantly get the answer. I can achieve the same with CF app,
however the URL is going to be different every month, e.g:

https://commitfest.postgresql.org/55/?text=&status=-1&targetversion=-1&author=-3&reviewer=-1&sortkey=

Occasionally CI may fail not because something is wrong with my patch.
In such cases the "CI status" column shows me a red icon and something
like "9/10". A few extra clicks are needed for every patch to
understand what happened. When using cfbot I see right away that
something went wrong on Windows for almost all the patches, as an
example.

I could leave without cfbot but this would make my workflow less convenient.



pgsql-hackers by date:

Previous
From: Greg Burd
Date:
Subject: [PATCH] bms_prev_member() can read beyond the end of the array of allocated words
Next
From: Jelte Fennema-Nio
Date:
Subject: Re: cfbot mistakenly reports that a rebase is needed