You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by James Goodall <jg...@dmetrix.com> on 2003/06/21 22:33:38 UTC
make check failures on 0.24.x
(continued from thread Re: Subversion 0.24.1 released.)
I have been completely unable to make subversion 0.24.1 or 0.24.2 pass all
of its tests on Redhat 7.3. This is a new issue for me as of 0.24.x because
I've been able to make and test previous versions successfully. When I try
'make check' with 0.23.0 already installed, I get:
FAIL: svnversion_tests.py 1: test 'svnversion' on a working copy and other
directories
After discussing the issue on this list a few days ago with Philip Martin, I
tried his suggestion of deleting my current installation and trying again.
After trying: rm /usr/local/lib/libsvn* /usr/local/bin/svn*, I now get the
following failures:
FAIL: getopt_tests.py 2: run svn --version
FAIL: getopt_tests.py 3: run svn --version --quiet
FAIL: getopt_tests.py 4: run svn --help
FAIL: getopt_tests.py 5: run svn help
FAIL: getopt_tests.py 6: run svn help --version
FAIL: getopt_tests.py 7: run svn help bogus-cmd
FAIL: getopt_tests.py 8: run svn help log switch
FAIL: basic_tests.py 1: basic checkout of a wc
FAIL: commit_tests.py 1: commit one file.
FAIL: update_tests.py 1: update a locally-modified binary file
FAIL: switch_tests.py 1: test some basic switching operations
FAIL: prop_tests.py 1: write/read props in wc only (ps, pl, pdel)
FAIL: schedule_tests.py 1: schedule: add some files
FAIL: log_tests.py 1: 'svn log', no args, top of wc.
FAIL: copy_tests.py 1: basic copy and move commands -- on files only
FAIL: diff_tests.py 1: update a file
FAIL: externals_tests.py 1: check out a directory with some external
modules attached
FAIL: merge_tests.py 1: performing a merge, with mixed results
FAIL: stat_tests.py 1: run status on an unversioned file in the current
directory
FAIL: trans_tests.py 1: commit new files with keywords active from birth
FAIL: svnadmin_tests.py 1: test 'svnadmin create' subcommand
FAIL: svnlook_tests.py 1: test 'svnlook youngest' subcommand
FAIL: svnversion_tests.py 1: test 'svnversion' on a working copy and other
directories
What's changed between 0.23 and 0.24 that I can't pass these tests
successfully? I'm building against httpd 2.0.46 and db 4.1.25 (exactly the
same as previous svn version builds).
- James
Re: make check failures on 0.24.x
Posted by Philip Martin <ph...@codematters.co.uk>.
"James Goodall" <jg...@dmetrix.com> writes:
> FAIL: getopt_tests.py 2: run svn --version
That's not really enough information to diagnose the problem, you need
to look at the errors in tests.log.
--
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
RE: make check failures on 0.24.x
Posted by James Goodall <jg...@dmetrix.com>.
Never mind. I tracked the problem down to the fact that you should never
give the root password of the software server to a manager, even if he
insists (he accidentally changed some file permissions - specifically, my
~/.subversion directory and files).
- James
-----Original Message-----
From: James Goodall [mailto:jgoodall@dmetrix.com]
Sent: Saturday, June 21, 2003 3:34 PM
To: Subversion Dev List
Subject: make check failures on 0.24.x
(continued from thread Re: Subversion 0.24.1 released.)
I have been completely unable to make subversion 0.24.1 or 0.24.2 pass all
of its tests on Redhat 7.3. This is a new issue for me as of 0.24.x because
I've been able to make and test previous versions successfully. When I try
'make check' with 0.23.0 already installed, I get:
FAIL: svnversion_tests.py 1: test 'svnversion' on a working copy and other
directories
After discussing the issue on this list a few days ago with Philip Martin, I
tried his suggestion of deleting my current installation and trying again.
After trying: rm /usr/local/lib/libsvn* /usr/local/bin/svn*, I now get the
following failures:
FAIL: getopt_tests.py 2: run svn --version
FAIL: getopt_tests.py 3: run svn --version --quiet
FAIL: getopt_tests.py 4: run svn --help
FAIL: getopt_tests.py 5: run svn help
FAIL: getopt_tests.py 6: run svn help --version
FAIL: getopt_tests.py 7: run svn help bogus-cmd
FAIL: getopt_tests.py 8: run svn help log switch
FAIL: basic_tests.py 1: basic checkout of a wc
FAIL: commit_tests.py 1: commit one file.
FAIL: update_tests.py 1: update a locally-modified binary file
FAIL: switch_tests.py 1: test some basic switching operations
FAIL: prop_tests.py 1: write/read props in wc only (ps, pl, pdel)
FAIL: schedule_tests.py 1: schedule: add some files
FAIL: log_tests.py 1: 'svn log', no args, top of wc.
FAIL: copy_tests.py 1: basic copy and move commands -- on files only
FAIL: diff_tests.py 1: update a file
FAIL: externals_tests.py 1: check out a directory with some external
modules attached
FAIL: merge_tests.py 1: performing a merge, with mixed results
FAIL: stat_tests.py 1: run status on an unversioned file in the current
directory
FAIL: trans_tests.py 1: commit new files with keywords active from birth
FAIL: svnadmin_tests.py 1: test 'svnadmin create' subcommand
FAIL: svnlook_tests.py 1: test 'svnlook youngest' subcommand
FAIL: svnversion_tests.py 1: test 'svnversion' on a working copy and other
directories
What's changed between 0.23 and 0.24 that I can't pass these tests
successfully? I'm building against httpd 2.0.46 and db 4.1.25 (exactly the
same as previous svn version builds).
- James