bug-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: repository is broken


From: Pavel Roskin
Subject: Re: repository is broken
Date: Fri, 27 Apr 2001 20:14:10 -0400 (EDT)

Hello, Larry!

> It wouldn't help -- this particular breakage wasn't detected by the test
> suite (or it wouldn't have been released).  And it would make it very
> hard to test a local-only CVS.

I see. I never considered the fact the the local-only cvs should pass the
testsuite.

> Agreed.  There were test cases added to sanity.sh to catch the problem
> that broke 1.10.6 and I'm in the process of adding test cases to catch
> this most recent problem.

Great. I appreciate it. The new "pserver" test passes in the remote mode
(RedHat 7.0, i686).

However, "modules5" fails in the remote mode:

PASS: modules5-7
** expected:
U realmodule/a
cvs [a-z]*: Executing ../tmp/cvs-sanity/cvsroot/checkout\.sh. .realmodule..
checkout script invoked in .*
args: realmodule
** got:
U realmodule/a
checkout script invoked in /tmp/cvs-serv13285
args: realmodule
cvs server: Executing ''/tmp/cvs-sanity/cvsroot/checkout.sh' 'realmodule''
FAIL: modules5-8

It seems to be a trivial problem with sorting the output. However, this
makes me wonder if "make remotecheck" is a part of the release procedure.

Maybe "make check" should include the remote testing? The later should
exit gracefully (i.e. with code 0) if the binary doesn't include server
support (now it fails).

-- 
Regards,
Pavel Roskin




reply via email to

[Prev in Thread] Current Thread [Next in Thread]