Thread: "CVS-Unknown" buildfarm failures?
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
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 solutionssince 1997 http://www.commandprompt.com/
Tom Lane said:
> 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 ...
>
cvs-unknown means there are unknown files in the repo:
my $unknown_files = grep {/^\?/ } @cvslog;
... send_result('CVS-Unknown',$unknown_files,\@cvslog) if ($unknown_files);
This is almost always a case of operator error. buildfarm only ever builds
in a copy of the repo, not in the permanent repo itself, so there should
NEVER be any file there which does not come from CVS. I have repeatedly
advised buildfarm member owners not to build by hand in the buildfarm repos.Not everybody listens, apparently.
All this is intended to ensure that we are actually working on a faithful
reflection of the postgresql.org repo, and not something that has been
mangled somehow.
I can call it "CVS-Unknown-Files" if that will make it clearer.
cheers
andrew
Joshua D. Drake said: > Tom Lane wrote: >> >> 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. > If that doesn't work, the correct method of recovery is to remove the repo copy altogether and let the buildfarm script get a completely fresh checkout: rm -rf <buildroot>/<branch>/pgsql would do the trick. cheers andrew
"Andrew Dunstan" <andrew@dunslane.net> writes:
> Tom Lane said:
>> 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.
> cvs-unknown means there are unknown files in the repo:
Oh. Well, it needs renamed then ;-). Per our message style guidelines,
calling an error "unknown" is seldom a good idea.
> I can call it "CVS-Unknown-Files" if that will make it clearer.
Maybe CVS-Extraneous-Files?
regards, tom lane