Actually, I think fs-test.c should delete the databases before it
runs. That way, the databases stick around for post-mortem analysis,
but you can run fs-test repeatedly --- say, from GDB.
The Berkeley DB library contains a function for deleting databases.
"B. W. Fitzpatrick" <fitz@red-bean.com> writes:
> Good point. If you're working on a bug and need the filesystem to stay
> around, you would just run it by hand and not from make check.
>
> Patch applied.
>
> -Fitz
>
> > Index: run-fs-tests.sh
> > ===================================================================
> > RCS file: /cvs/subversion/subversion/tests/libsvn_fs/run-fs-tests.sh,v
> > retrieving revision 1.2
> > diff -u -r1.2 run-fs-tests.sh
> > --- run-fs-tests.sh 2000/12/17 00:13:50 1.2
> > +++ run-fs-tests.sh 2001/03/01 07:06:58
> > @@ -2,8 +2,8 @@
> > #### run-fs-tests.sh --- run filesystem test programs
> >
> > ## Remove database files cretaed by the tests.
> > -if [ -d test-repo ]; then
> > - rm -fr test-repo;
> > +if [ -d test-repo-1 ]; then
> > + rm -fr test-repo-*;
> > fi
> >
> > > ./tests.log
> >
> > --
> > Yoshiki Hayashi
> >
>
>
Received on Sat Oct 21 14:36:23 2006