On 12/13/05, Garrett Rooney <rooneg@electricjellyfish.net> wrote:
> On 12/13/05, svn-builder@shadyvale.net <svn-builder@shadyvale.net> wrote:
>
> > At least one test FAILED, checking D:\tests-svn\svn-tests.log
> > FAIL: commit_tests.py 34: post commit hook failure case testing
> > FAIL: prop_tests.py 11: set, get, and delete a revprop change
> > FAIL: log_tests.py 10: svn log --xml must not print empty date elements
> > FAIL: trans_tests.py 8: keyword expanded on cat
> > At least one test was SKIPPED, checking D:\tests-svn\svn-tests.log
>
> Ok, I'm confused. This says that these tests failed, but they show up
> as passed in the attached test.log.gz file. Is this machine not
> attaching the correct test output, or is it looking at the wrong
> output when it looks for failures, or what? Perhaps fallout from the
> subversion/tests/svn -> subversion/tests/cmdline thing?
Yes, the wrong test log was attached...my fault. That should be fixed now.
The first failure (hook) is due to a relative path in the hook -- the
svnserve process is not being started with a working directory of
where the hook is assuming it will be, I think. I'm not sure if the
hook should have an absolute path or if the svnserve process should be
started with a specific working directory? I don't think the tests
used to require that, but I'm not sure.
I haven't looked at the other failures yet, but they may be related.
DJ
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Dec 14 01:03:14 2005