Re: extraneous output from sanity

[Paul Edwards]

> I'm not seeing that behavior, so if you could determine exactly which
> sanity.sh line is printing that, it would be helpful.

I have determined the line, and tested the below fix and it works,
ie no more spurious messages.  I didn't investigate why this cd
echos but other cd's don't.  I normally run bash, and the platform
is Solaris 8.

> There are only
> about 24 backuprecover tests, so a few runs with a few extra echo
> statements would probably be enough to locate it.

And indeed it was.

> Also, what version of CVS are you seeing that in?

1.11.23

Patch below is against that version.

BTW, thanks for 1.11.23 - I have confirmed that it fixes the problem
I reported some years ago about CVS not detecting a remove
conflict.  So finally my site can run an unmodified CVS.  :-)

BFN.  Paul.



cvs diff -c sanity.sh
Index: sanity.sh
===================================================================
RCS file: /development/repository/ccvs/src/sanity.sh,v
retrieving revision 1.1.1.1
diff -c -r1.1.1.1 sanity.sh
*** sanity.sh   10 Sep 2008 04:24:38 -0000      1.1.1.1
--- sanity.sh   11 Sep 2008 02:59:05 -0000
***************
*** 21772,21778 ****
 # version of a newly recovered repository and replace the CVS
 # database dirs in a workspace with later revisions than those in the
 # recovered repository
! cd repos-first-dir
 DATADIRS=\`find . -name CVS -print\`
 cd ../first-dir
 find . -name CVS -print | xargs rm -rf
--- 21772,21778 ----
 # version of a newly recovered repository and replace the CVS
 # database dirs in a workspace with later revisions than those in the
 # recovered repository
! cd ./repos-first-dir
 DATADIRS=\`find . -name CVS -print\`
 cd ../first-dir
 find . -name CVS -print | xargs rm -rf




> Paul Edwards wrote:
> > I assume that the "backuprecover" stuff isn't meant to be printed?
> >
> > Otherwise all fine.
> >
> > BFN.  Paul.
> >
> >
> >
> >
> > This test should produce no other output than this message, and a final
> > "OK". (Note that the test can take an hour or more to run and
> > periodically stops
> > for as long as one minute.  Do not assume there is a problem just
> > because nothing seems to happen for a long time.  If you cannot live
> > without running status, use the -v option or try the command: `tail -f
> > check.log' from another window.)
> > /tmp/cvs-sanity/backuprecover/4/repos-first-dir
> > /tmp/cvs-sanity/backuprecover/3/repos-first-dir OK, all 3268 tests 
> > passed.
> >
> >
> > _______________________________________________
> > Bug-cvs mailing list
> > Bug-cvs@nongnu.org
> > http://lists.nongnu.org/mailman/listinfo/bug-cvs
>
>
> --
> Derek R. Price
> Solutions Architect
> Ximbiot, LLC <http://ximbiot.com>
> Get CVS and Subversion Support from Ximbiot!
>
> v: +1 248.835.1260
> f: +1 248.246.1176