[cvs] bogofilter/tests t.frame,1.24,1.25

David Relson relson at osagesoftware.com
Tue Jan 21 01:02:17 CET 2003


At 06:48 PM 1/20/03, Matthias Andree wrote:

>relson at users.sourceforge.net writes:
>
> > Update of /cvsroot/bogofilter/bogofilter/tests
> > In directory sc8-pr-cvs1:/tmp/cvs-serv7974
> >
> > Modified Files:
> >       t.frame
> > Log Message:
> > Ensure output directory is empty at start of test.
> >
>
>It's been a long time since I've last had a look at the code, but this
>ultimately breaks the unique name generation we're doing here. I'm
>cleaning this up now, CVS commit in a few minutes.


Slow down!  I changed it for a reason.  Today I experienced a variety of 
peculiar results.  I was running "make -s check" variously from my cvs and 
tst hierarchies.  I was running with BF_TESTDIR=/mnt/ramdrive and 
SUPPRESS_DELETE=NO because having a test fail without leaving any evidence 
is just a source of trouble.  I saw tests that would succeed sometimes and 
fail other times.  t.robx once generated a 0.16 value which is very, very 
wrong.  I guessed it was files getting left behind, so changed t.frame to 
ensure that the directories are empty at the start of the test.  It would 
be O.K. to make the emptying subject to SUPPRESS_DELETE=NO.





More information about the bogofilter-dev mailing list