From: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Aleksander Alekseev <aleksander(at)tigerdata(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
Subject: | Re: cfbot mistakenly reports that a rebase is needed |
Date: | 2025-08-13 20:27:04 |
Message-ID: | CAGECzQSSskLnB5kNNR7KPAxNd5HbRR2hB+_Gk3-W6v5xD9Gw3A@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 13 Aug 2025 at 16:39, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Aleksander Alekseev <aleksander(at)tigerdata(dot)com> writes:
> > I keep an eye on my patches using cfbog [1] and I think since recently
> > it started to mistakenly mark patches as "needs rebase" while in fact
> > everything is OK. If we take [2] for instance, it applies fine:
>
> Yeah, I have observed the same with my patches (according to [1],
> two of 'em need rebase right now, though the underlying 'git am' logs
> report success). In some past occurrences the gripe has gone away
> without my doing anything...
>
> regards, tom lane
>
> [1] http://cfbot.cputube.org/tom-lane.html
Took a quick look, and publicly noting my findings: Interestingly none
of these patches show up as "needs rebase" in the commitfest app. So
it seems that this is a cfbot webpage generation bug.
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2025-08-13 21:07:07 | Re: index prefetching |
Previous Message | Jim Nasby | 2025-08-13 20:06:16 | Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem) |