From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | "CVS-Unknown" buildfarm failures? |
Date: | 2006-06-01 22:33:18 |
Message-ID: | 22014.1149201198@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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 ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2006-06-01 23:04:46 | Re: "CVS-Unknown" buildfarm failures? |
Previous Message | Tom Lane | 2006-06-01 21:53:14 | Re: pgsql: Fix calculation of plan node extParams to account for the |