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

mingw test failures

From: Martin Hauner <hauner_at_web.de>
Date: Mon, 12 Oct 2009 23:07:47 +0200


I'm currently trying to build subversion with mingw. After starting with a lot
of test failures (I think it were 249 test failures or something like that) I'm
down to 5 test failures after a few minimal changes and acouple of rebuilds:

At least one test FAILED, checking c:\Development\mingw\svn-1.6.x\tests.log
FAIL: dirent_uri-test.exe 18: test svn_dirent_get_absolute
FAIL: commit_tests.py 22: commit from a dir with a longer name than the wc
FAIL: update_tests.py 27: conflict markers should match the file's eol style
FAIL: prop_tests.py 13: some svn: properties should be converted
FAIL: merge_tests.py 40: conflict markers should match the file's eol style
Summary of test results:
   43 tests SKIPPED
   25 tests XFAILED
   5 tests FAILED

The dirent_uri-test.exe fails in test_dirent_get_absolute { "C:abc", "@/abc" }.
But this is a binary where I can simply run it with gdb.

My question is how do I debug svn inside the python tests?

I tried to replace the svn binary (svn_binary in svntest/main.py) with a script
that calls gdb. But that doesn't seem to work. It just stops and I don't get a
gdb prompt although gdb is running (I can see it in the task mananger).

Subcommander 2.0.0 Beta 5 - http://subcommander.tigris.org
a Win32/Unix/MacOSX subversion GUI client & diff/merge tool.
Received on 2009-10-13 23:47:57 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.