On Wed, 2002-04-03 at 17:50, cmpilato@collab.net wrote:
> Ben Collins-Sussman <sussman@red-bean.com> writes:
>
> > > Stop using the trace-commit editor in a half-XXXed way. Instead, send
> > > detailed feedback to the application that *looks* like the old
> > > trace-commit editor output. This should cause our python tests to
> > > pass again with the new commit system.
> >
> > Ha, well, basic_tests.py passes, which does a lot of committing. But
> > now several tests within the very large commit_tests.py are failing.
> > (numbers 4, 5, 6, 7, 11, 14, 15).
>
> Ben, a big phat public thanks for helping me out with this stuff
> today. I'm looking at the failing tests now. Have fixed 4, 5, and 7.
> I know why 11 fails (unfinished work). 14 and 15 remain. Oh. And
> I've broken 9. :-\
copy_tests.py #1 fails too. Very amusing output!
subversion/libsvn_client/commit.c:548
svn_error: #21002 : <A general problem occured>
Commit succeeded, but other errors follow:
subversion/libsvn_client/commit.c:570
apr_error: #20, src_err 0 : <Not a directory>
Error bumping revisions post-commit:
subversion/libsvn_client/commit.c:568
apr_error: #20, src_err 0 : <Not a directory>
-------------------------------------------------
subversion/libsvn_wc/adm_files.c:627
apr_error: #20, src_err 0 : <Not a directory>
/usr/home/sussman/projects/svn/subversion/tests/clients/cmdline/
working_copies/copy_tests-1/A/B/F/iota/.svn/entries
Received on Thu Apr 4 01:55:53 2002