From: Tom Lane <tgl@sss.pgh.pa.us>
To: Thomas Munro <thomas.munro@gmail.com>
cc: pgsql-hackers <pgsql-hackers@postgresql.org>, rosset.filipe@gmail.com
Subject: Re: How did queensnake corrupt zic.o?
In-reply-to: <CA+hUKGKh+mFzMPT4Gs0a=GOtEmWy3+vb=sJQQVLk5B-e=-JBxw@mail.gmail.com>
References: <CA+hUKGKh+mFzMPT4Gs0a=GOtEmWy3+vb=sJQQVLk5B-e=-JBxw@mail.gmail.com>
Comments: In-reply-to Thomas Munro <thomas.munro@gmail.com>
	message dated "Mon, 14 Feb 2022 18:29:28 +1300"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2781552.1644819918.1@sss.pgh.pa.us>
Date: Mon, 14 Feb 2022 01:25:18 -0500
Message-ID: <2781553.1644819918@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/2781553.1644819918%40sss.pgh.pa.us>
Precedence: bulk

Thomas Munro <thomas.munro@gmail.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