Re: Tom Lane
> Many kilowatt-hours later, I've entirely failed to reproduce this
> on gcc230. Not sure how to investigate further. Given that your
> original build machine is so slow, could it be timing-related?
> Hard to see how, given the location of the crash, but ...
My other rebuild (on yet
I wrote:
> I see that the gcc farm[1] has another mips64 machine running Debian
> buster, so I've started a build there to see what happens.
Many kilowatt-hours later, I've entirely failed to reproduce this
on gcc230. Not sure how to investigate further. Given that your
original build machine is
Re: To Tom Lane
> > Is the crash 100% reproducible for you?
>
> I have scheduled a rebuild now, we'll know in a few hours...
The build was much faster this time (different machine), and worked.
https://buildd.debian.org/status/logs.php?pkg=postgresql-15&arch=mips64el
I'll also start a test buil
Christoph Berg writes:
> Re: Tom Lane
>> Hmm, so what's different between this and buildfarm member topminnow?
> That one is running Debian jessie (aka oldoldoldoldstable), uses
> -mabi=32 with gcc 4.9, and runs a kernel from 2015.
> The Debian buildd is this:
> https://db.debian.org/machines.cg
Re: Tom Lane
> Christoph Berg writes:
> > Debian unstable mips64el:
>
> Hmm, so what's different between this and buildfarm member topminnow?
That one is running Debian jessie (aka oldoldoldoldstable), uses
-mabi=32 with gcc 4.9, and runs a kernel from 2015.
The Debian buildd is this: https://d
Re: Tom Lane
> Christoph Berg writes:
> > Debian unstable mips64el:
>
> Hmm, so what's different between this and buildfarm member topminnow?
>
> Is the crash 100% reproducible for you?
I have scheduled a rebuild now, we'll know in a few hours...
Christoph
Christoph Berg writes:
> Debian unstable mips64el:
Hmm, so what's different between this and buildfarm member topminnow?
Is the crash 100% reproducible for you?
regards, tom lane
Debian unstable mips64el:
2022-05-18 22:57:34.436 UTC client backend[19222] pg_regress/triggers
STATEMENT: drop trigger trg1 on trigpart3;
...
2022-05-18 22:57:39.110 UTC postmaster[7864] LOG: server process (PID 19222)
was terminated by signal 11: Segmentation fault
2022-05-18 22:57:39.110 UT
