Lübbe Onken wrote:
> On second thought: It might be a good idea to require a test directory
> to be given on the command line before allowing the tests to be run, if
> the tests are bound to fail otherwise.
Good idea. It's always failed unless I pass the test directory so I've
always just done that and forgot about it. Perhaps someone else
(Brane?) knows if it is supposed to be optional or not?
>
> While I'm writing this mail, the tests are still cranking along and I
> also get a failure in commit_tests.py
> The tests are at copy_tests.py now, but I have to leave. If there are
> any other failures, I report them tomorrow.
>
> I'm running rev 7461 which I compiled some time this morning to play
> around with the blame command.
>
Make sure the *case* of the test directory you pass is correct or one of
the commit tests fails (commit-test-22 IIRC). Yes, kind of picky.
DJ
**********************************************************************
This email and any files transmitted with it are confidential
and intended solely for the use of the individual or entity to
whom they are addressed. If you have received this email
in error please notify the system manager.
This footnote also confirms that this email message has been
swept by MIMEsweeper for the presence of computer viruses.
www.mimesweeper.com
**********************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Oct 21 17:42:38 2003