Skip site navigation (1) Skip section navigation (2)

Re: "CVS-Unknown" buildfarm failures?

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: "CVS-Unknown" buildfarm failures?
Date: 2006-06-01 23:04:46
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Tom Lane wrote:
> meerkat and snake both have persistent "CVS-Unknown" failures in some
> but not all branches.  I can't see any evidence of an actual failure
> in their logs though.  What I do see is "?" entries about files that
> shouldn't be there --- for instance, meerkat apparently needs a "make
> distclean".  If that's what's causing the failure report, could we
> get the buildfarm to show a more useful status message?  I'd always
> assumed that "CVS-Unknown" suggested a transient problem such as
> connection loss, and there wasn't any need for human intervention.
> A more radical answer is to have the script go ahead and delete the
> offending files itself, but I can see where that might not have good
> fail-soft behavior ...

I have manually ran a dist-clean on meerkat for 8_0 and 8_1 and am 
rerunning the builds now.

Joshua D. Drake

> 			regards, tom lane
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster


    === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
    Providing the most comprehensive  PostgreSQL solutions since 1997

In response to


pgsql-hackers by date

Next:From: Jim C. NasbyDate: 2006-06-01 23:09:48
Subject: Re: More thoughts about planner's cost estimates
Previous:From: Tom LaneDate: 2006-06-01 22:33:18
Subject: "CVS-Unknown" buildfarm failures?

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group