public inbox for [email protected]  

help / color / mirror / Atom feed

From: Andrew Dunstan <[email protected]>
To: Todd A. Cook <[email protected]>
To: Tom Lane <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: Help with failures on HEAD
Date: Fri, 10 Feb 2023 10:42:31 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>


On 2023-02-09 Th 14:00, Todd A. Cook wrote:
>      On 2/9/23, 1:41 PM, "Tom Lane" <[email protected]  <mailto:[email protected]>> wrote:
>      "Todd A. Cook" <[email protected]  <mailto:[email protected]>> writes:
>      > Hi,
>      > Last Saturday morning, builds of HEAD on my animal mantid[1] spontaneously started failing;
>      > see [2] for an example. The log shown there is
>
>      > Missing checked out branch bf_HEAD:
>      > * [32mbf_HEAD[m
>      > bf_REL_11_STABLE[m
>      > bf_REL_12_STABLE[m
>      > bf_REL_13_STABLE[m
>      > bf_REL_14_STABLE[m
>      > bf_REL_15_STABLE[m
>      > master[m
>
>      In the past, I've been able to resolve issues similar to this one
>      by flushing the animal's git repo (rm -rf pgmirror.git) and letting
>      it pull that down fresh on the next run. Not clear if you included
>      that when you "removed the buildroot"?
>
> Yes, I did "rm -rf buildroot".  After that, I verified (with "diff -r") that I had no changes
> vs. the distribution tarball other than having my build-farm.conf present.


Don't do that. All the state is stored under the buildroot, and you'd be 
throwing that away. 999 times out of 1000 this should do the trick:


rm -rf buildroot/[RH]*/pgsql


The other 1 time out of 1000 you could also remove the mirror like Tom 
suggests as well.


cheers


andrew


--
Andrew Dunstan
EDB:https://www.enterprisedb.com

view thread (8+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Help with failures on HEAD
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox