[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

make check (svn 1.1.0): lots of FAILUREs

From: Tobias Herp <tobias.herp_at_gmx.de>
Date: 2004-10-04 22:47:35 CEST

Hi,

I'm currently trying to install svn 1.1.0 on my vServer running SuSE:

   ./configure "--with-apr=/usr/local/apache-2.0.51" \
   "--with-apr-util=/usr/local/apache-2.0.51" \

   make

So far, everything works fine; but

   make check

yields:

www:~/download/subversion-1.1.0 # make check
Running all tests in config-test...success
Running all tests in diff-diff3-test...FAILURE
Running all tests in hashdump-test...success
Running all tests in path-test...success
Running all tests in random-test...FAILURE
Running all tests in stream-test...success
Running all tests in string-test...success
Running all tests in time-test...success
Running all tests in translate-test...success
Running all tests in utf-test...success
Running all tests in target-test.py...success
Running all tests in getopt_tests.py...success
Running all tests in basic_tests.py...FAILURE
Running all tests in commit_tests.py...FAILURE
Running all tests in update_tests.py...FAILURE
Running all tests in switch_tests.py...FAILURE
Running all tests in prop_tests.py...FAILURE
Running all tests in schedule_tests.py...FAILURE
Running all tests in log_tests.py...FAILURE
Running all tests in copy_tests.py...FAILURE
Running all tests in diff_tests.py...FAILURE
Running all tests in export_tests.py...FAILURE
Running all tests in externals_tests.py...FAILURE
Running all tests in merge_tests.py...FAILURE
Running all tests in revert_tests.py...FAILURE
Running all tests in stat_tests.py...FAILURE
Running all tests in trans_tests.py...FAILURE
Running all tests in autoprop_tests.py...FAILURE
Running all tests in blame_tests.py...FAILURE
Running all tests in special_tests.py...FAILURE
Running all tests in svnadmin_tests.py...FAILURE
Running all tests in svnlook_tests.py...FAILURE
Running all tests in svnversion_tests.py...FAILURE
Running all tests in run-fs-tests.py...Traceback (most recent call
last):
   File "./build/run_tests.py", line 197, in ?
     main()
   File "./build/run_tests.py", line 190, in main
     failed = th.run(args[4:])
   File "./build/run_tests.py", line 39, in run
     failed = self._run_test(prog) or failed
   File "./build/run_tests.py", line 113, in _run_test
     failed = self._run_prog(progname, cmdline)
   File "./build/run_tests.py", line 143, in _run_prog
     rv = os.spawnv(os.P_WAIT, progname, cmdline)
   File "/usr/local/lib/python2.3/os.py", line 521, in spawnv
     return _spawnvef(mode, file, args, None, execv)
   File "/usr/local/lib/python2.3/os.py", line 504, in _spawnvef
     wpid, sts = waitpid(pid, 0)
KeyboardInterrupt
make: *** [check] Fehler 1

(the script hangs at the run-fs-tests)

I re-configured:

   ./configure "--with-apr=/usr/local/apache-2.0.51" \
   "--with-apr-util=/usr/local/apache-2.0.51" \
   "--without-berkeley-db"

   make

.... now "make check" (or "make fsfscheck", since I have no
BerkeleyDB installed) doesn't hang anymore, but the tests still
fail. I even tried

   make clean

   ./configure "--with-apr=/usr/local/apache-2.0.51" \
   "--with-apr-util=/usr/local/apache-2.0.51" \
   "--without-berkeley-db"

   make

but this didn't change anything.

Last thing I tried is that I did "make install" before "make
fsfscheck"ing again; the log grew somewhat longer, since some usage
info is output, but the tests still fail.

How serious are the (many!) FAILUREs? Any ideas how to get rid of
them? Is anyone interested in my tests.logs?

Thanks in advance,

Tobias

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Oct 4 22:48:12 2004

This is an archived mail posted to the Subversion Users mailing list.