e.huelsmann@gmx.net wrote:
> Could you check if these problems were introduced at revision 6994?
> (ie by running test on revision 6993 and 6994) Major changes
> to the test suite have been committed in rev 6994 maybe something
> has slipped through.
I don't think so -- I've been seeing the update-15 test fail for a
while, just haven't had time to look at it closely and the new trans
test failure looks exactly the same.
To fix the trans test it looks like this method needs to be fixed:
def _tweak_paths(list):
if os.sep != "/":
tweaked_list = []
for line in list:
tweaked_list.append(string.replace(line, os.sep, "/"))
return tweaked_list
else:
return list
Aren't the last two parameters to the string.replace call backwards?
And the update 15 test needs the same tweaking it looks like -- is the
_tweak_paths method the way this is supposed to be handled?
As I mentioned below, hopefully I can look at the commit test failure
soon in more detail -- it acts like it is missing the chdir call or
something which causes Subversion to display just the filename and not a
full path.
DJ
>
> bye,
>
> Erik.
>
>
>>I'm getting a new test failure on Windows for r7000 -- I'm not sure
>>when it was introduced, but I last ran them a few days ago and didn't
>>see the trans_test.py 6 failure.
>>
>>D:\Projects\Subversion>win-tests.py -r c:\temp\junk
>>Testing Release configuration on local repository.
>>Running all tests in config-test.exe...success
>>Running all tests in hashdump-test.exe...success
>>Running all tests in string-test.exe...success
>>Running all tests in path-test.exe...success
>>Running all tests in stream-test.exe...success
>>Running all tests in time-test.exe...success
>>Running all tests in translate-test.exe...success
>>Running all tests in diff-diff3-test.exe...success
>>Running all tests in random-test.exe...success
>>Running all tests in target-test.py...success
>>Running all tests in run-fs-tests.py...success
>>Running all tests in run-repos-tests.py...success
>>Running all tests in getopt_tests.py...success
>>Running all tests in basic_tests.py...success
>>Running all tests in commit_tests.py...FAILURE
>>Running all tests in update_tests.py...FAILURE
>>Running all tests in switch_tests.py...success
>>Running all tests in prop_tests.py...success
>>Running all tests in schedule_tests.py...success
>>Running all tests in log_tests.py...success
>>Running all tests in copy_tests.py...success
>>Running all tests in diff_tests.py...success
>>Running all tests in externals_tests.py...success
>>Running all tests in merge_tests.py...success
>>Running all tests in stat_tests.py...success
>>Running all tests in trans_tests.py...FAILURE
>>Running all tests in svnadmin_tests.py...success
>>Running all tests in svnlook_tests.py...success
>>Running all tests in svnversion_tests.py...success
>>At least one test FAILED, checking c:\temp\junk\tests.log
>>FAIL: commit_tests.py 22: commit from a dir with a longer name than the
>>wc
>>FAIL: update_tests.py 15: another "hudson" problem: updates that delete
>>FAIL: trans_tests.py 6: committing eol-style change forces text send
>>At least one test was SKIPPED, checking c:\temp\junk\tests.log
>>SKIP: basic_tests.py 18: basic import of executable files
>>SKIP: commit_tests.py 28: committing a symlink should fail
>>SKIP: prop_tests.py 11: set and get a revprop change
>>SKIP: schedule_tests.py 4: schedule: add some executable files
>>SKIP: schedule_tests.py 10: revert: add some executable files
>>SKIP: schedule_tests.py 16: commit: add some executable files
>>SKIP: copy_tests.py 11: executable bit should be preserved when copying
>>SKIP: stat_tests.py 6: status on versioned items replaced by symlinks
>>
>>FAIL: D:\Projects\Subversion\win-tests.py
>>
>>
>>The failed commit is not new and appears to be related to the observed
>>Windows FS problem which I'm about ready to give up on (I'm going to be
>>analyzing the test failure and perhaps use a new approach based on it
>>sometime soon, since it doesn't fail quite the same as the 'access
>>denied' errors seen elsewhere).
>>
>>The other failures appear to be due to backslashes where it expects
>>slashes, which is probably ok on Windows?
>>
>>In all cases, manually running them appears to work fine -- the output
>>just doesn't quite match up with what the test expected, I think.
>>
>>The log is at http://www.shadyvale.net/svn/tests.log if anyone cares to
>>take a look.
>>
>>DJ
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Sep 7 21:45:05 2003