Re: How did queensnake corrupt zic.o?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, rosset(dot)filipe(at)gmail(dot)com
Subject: Re: How did queensnake corrupt zic.o?
Date: 2022-02-14 06:25:18
Message-ID: 2781553.1644819918@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> We see a successful compile and then a failure to read the file while
> linking. We see that the animal got into that state recently and then
> fixed itself, and now it's back in that state. I don't know if it's
> significant, but it happened to fix itself when a configure change
> came along, which might be explained by ccache invalidation; that is,
> the failure mode doesn't depend on the input files, but once it's
> borked you need a change to kick ccache. My memory may be playing
> tricks on me but I vaguely recall seeing another animal do this, a
> while back.

queensnake's seen repeated cycles of unexplainable build failures.
I wonder if it's using a bogus ccache version, or if the machine
itself is flaky.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2022-02-14 06:31:42 Re: pg_receivewal.exe unhandled exception in zlib1.dll
Previous Message Tom Lane 2022-02-14 06:18:48 sockaddr_un.sun_len vs. reality