I'm not seeing that behavior, so if you could determine exactly which sanity.sh line is printing that, it would be helpful. There are only about 24 backuprecover tests, so a few runs with a few extra echo statements would probably be enough to locate it.
Also, what version of CVS are you seeing that in? Thanks, Derek 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 > [email protected] > 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 _______________________________________________ Bug-cvs mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/bug-cvs
