On Fri, 2 May 2025 at 07:28, Robins Tharakan wrote:
>
>
So ideally if gcc fixes the issue (or if I fix something stupid in the way
> I am
> compiling gcc etc), the next buildfarm run should automatically go
> green soon after.
>
Does look like a gcc bug. Ideally should go green automatically (o
On Fri, 2 May 2025 at 06:57, Tom Lane wrote:
> Robins Tharakan writes:
> > On Thu, 1 May 2025 at 19:43, Dean Rasheed
> wrote:
> >> doc: Warn that ts_headline() output is not HTML-safe.
>
> > This commit looks harmless, but 2 separate machines are
> > failing on this commit (at the same point).
Robins Tharakan writes:
> On Thu, 1 May 2025 at 19:43, Dean Rasheed wrote:
>> doc: Warn that ts_headline() output is not HTML-safe.
> This commit looks harmless, but 2 separate machines are
> failing on this commit (at the same point).
It's hardly likely that a docs-only commit is the cause. D
Hi,
On Thu, 1 May 2025 at 19:43, Dean Rasheed wrote:
> doc: Warn that ts_headline() output is not HTML-safe.
>
> Backpatch-through: 13
>
>
This commit looks harmless, but 2 separate machines are
failing on this commit (at the same point).
For now, it appears more like a compiler bug. I have req
