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

Re: svn trunk r35114: FAIL (win32-xp VS2005)

From: Hyrum K. Wright <hyrum_wright_at_mail.utexas.edu>
Date: Fri, 09 Jan 2009 09:22:37 -0800

Paul Burba wrote:
> On Fri, Jan 9, 2009 at 11:30 AM, <buildbot_at_mobsol.be> wrote:
>> Full details are available at:
>> http://www.mobsol.be/buildbot/win32-xp%2520VS2005/builds/1588
>>
>> Author list: senthil
>>
>> Build Slave: djh-xp-vse2005
>>
>>
>> Subversion Buildbot
>> http://www.mobsol.be/buildbot/
>>
>>
>> Last 100 lines of the build log (step: Test fsfs+ra_local ):
>>
>> SKIP: authz_tests.py 7: test authz for log and tracing path changes
>> SKIP: authz_tests.py 8: test authz for checkout and update
>> SKIP: authz_tests.py 9: test authz for export with unreadable subfolder
>> SKIP: authz_tests.py 10: test authz for aliases
>> SKIP: authz_tests.py 11: test the authz validation rules
>> SKIP: authz_tests.py 12: test authz for locking
>> SKIP: authz_tests.py 13: authz issue #2712
>> SKIP: authz_tests.py 14: switched to directory, no read access on parents
>> At least one test XFAILED, checking M:\svn-auto-test\fsfs\tests.log
>> XFAIL: fs-test.exe 18: merging commit
>> XFAIL: locks-test.exe 9: able to reserve a name (lock non-existent path)
>> XFAIL: locks-test.exe 10: directory locks (kinda)
>> XFAIL: tree-conflict-data-test.exe 3: detect broken tree conflict data
>> XFAIL: basic_tests.py 38: remotely remove directories from two repositories
>>
>> XFAIL: checkout_tests.py 13: co handles obstructing paths scheduled for add
>>
>> XFAIL: update_tests.py 31: forced up fails with some types of obstructions
>>
>> XFAIL: update_tests.py 32: update wc on the root of a Windows (virtual) drive
>>
>> XFAIL: update_tests.py 33: update wc containing a replaced-with-history file
>>
>> XFAIL: update_tests.py 34: update handles obstructing paths scheduled for add
>>
>> XFAIL: update_tests.py 50: tree conflicts on update 2.3
>>
>> XFAIL: switch_tests.py 10: switch a file to a dir and back to the file
>>
>> XFAIL: switch_tests.py 21: forced switch detects tree conflicts
>>
>> XFAIL: log_tests.py 21: test log -c on range of changes
>>
>> XFAIL: diff_tests.py 28: diff a renamed directory
>>
>> XFAIL: diff_tests.py 49: diff URL against working copy with local mods
>>
>> XFAIL: diff_tests.py 50: diff -r1 of removed file to its local addition
>>
>> XFAIL: merge_tests.py 20: merge into missing must not break working copy
>>
>> XFAIL: merge_tests.py 33: merge a replacement of a directory
>>
>> XFAIL: merge_tests.py 34: replace both dir and one of its children
>>
>> XFAIL: merge_tests.py 39: conflict from merge of add over versioned file
>>
>> XFAIL: merge_tests.py 55: avoid repeated merges for cyclic merging
>>
>> XFAIL: merge_tests.py 72: merge target with non inheritable mergeinfo
>>
>> XFAIL: merge_tests.py 91: merge added subtree
>>
>> XFAIL: merge_tests.py 115: tree conflicts on merge, local commit 5.1
>>
>> XFAIL: merge_tests.py 116: tree conflicts on merge, local commit 5.2
>>
>> XFAIL: merge_tests.py 120: tree conflicts on merge, NO local commit 5.1
>>
>> XFAIL: merge_tests.py 121: tree conflicts on merge, NO local commit 5.2
>>
>> XFAIL: merge_tests.py 125: merge prior to rename src existence still dels src
>>
>> XFAIL: revert_tests.py 4: revert a moved file
>>
>> XFAIL: mergeinfo_tests.py 4: 'mergeinfo' with uninteresting source selection
>>
>> XFAIL: info_tests.py 2: info on added file
>>
>> XFAIL: tree_conflict_tests.py 8: up/sw dir: add onto add
>>
>> XFAIL: tree_conflict_tests.py 14: merge dir: del/rpl/mv onto not-same
>>
>> At least one test FAILED, checking M:\svn-auto-test\fsfs\tests.log
>> FAIL: basic_tests.py 41: basic relative url target using current dir
>>
>> FAIL: basic_tests.py 42: basic relative url target using other targets
>>
>> FAIL: basic_tests.py 45: basic relative url targets with peg revisions
>>
>> FAIL: commit_tests.py 50: set invalid revision props during remote mkdir
>>
>> FAIL: update_tests.py 21: update child before parent of a deleted tree
>>
>> FAIL: update_tests.py 29: update schedule-add copy of old rev
>>
>> FAIL: switch_tests.py 11: non-recursive switch
>>
>> FAIL: prop_tests.py 15: recursive property operations in BASE and WC
>>
>> FAIL: copy_tests.py 13: copy item to root of repository
>>
>> FAIL: copy_tests.py 26: svn cp oldrev-of-deleted-URL URL
>>
>> FAIL: copy_tests.py 27: test URL to URL copying edge case
>>
>> FAIL: copy_tests.py 49: copy added path to URL
>>
>> FAIL: copy_tests.py 63: copy old revision of wc dir to new dir
>>
>> FAIL: diff_tests.py 24: diff a prop change on a dir named explicitly
>>
>> FAIL: diff_tests.py 35: base->repos diff of moved file
>>
>> FAIL: diff_tests.py 42: test diffs at various depths
>>
>> FAIL: merge_tests.py 47: discontinuous merges produce correct mergeinfo
>>
>> FAIL: merge_tests.py 95: merge fails with renamed subtrees with mergeinfo
>>
>> FAIL: merge_tests.py 100: mergeinfo not set on subtree with empty mergeinfo
>>
>> FAIL: merge_tests.py 102: merge tries to delete a file of identical content
>>
>> FAIL: merge_tests.py 103: merge tries to delete identical sched-add file
>>
>> FAIL: merge_tests.py 104: merge tries to delete a file of different content
>>
>> FAIL: merge_tests.py 107: merge two successive edits to the same property
>>
>> FAIL: merge_tests.py 108: merge an EOL unification and set svn:eol-style
>>
>> FAIL: merge_tests.py 109: merge adds mergeinfo to subtrees correctly
>>
>> FAIL: blame_tests.py 1: annotate a file whose name contains a space
>>
>> FAIL: blame_tests.py 2: annotate a binary file
>>
>> FAIL: lock_tests.py 1: lock a file and verify that it's locked
>>
>> FAIL: lock_tests.py 2: commit a file and keep lock
>>
>> FAIL: lock_tests.py 3: commit a file and release lock
>>
>> FAIL: lock_tests.py 4: commit a locked file with a prop change
>>
>> FAIL: lock_tests.py 5: lock a file and verify lock breaking behavior
>>
>> FAIL: lock_tests.py 6: lock a file and verify lock stealing behavior
>>
>> FAIL: lock_tests.py 8: verify behavior when a lock in a wc is defunct
>>
>> FAIL: lock_tests.py 9: verify svn:needs-lock read-only behavior
>>
>> FAIL: lock_tests.py 10: verify svn:needs-lock behavior with defunct lock
>>
>> FAIL: lock_tests.py 11: verify lock removal on a deleted path
>>
>> FAIL: lock_tests.py 12: lock and unlock some files
>>
>> FAIL: lock_tests.py 13: verify removal of a directory with locks inside
>>
>> FAIL: lock_tests.py 14: verify status of lock in working copy
>>
>> FAIL: lock_tests.py 15: verify status of stolen lock
>>
>> FAIL: lock_tests.py 16: verify status of broken lock
>>
>> FAIL: lock_tests.py 17: verify error on locking non-existent file
>>
>> FAIL: lock_tests.py 18: lock an out-of-date file and ensure failure
>>
>> FAIL: lock_tests.py 19: update handles svn:needs-lock correctly
>>
>> FAIL: lock_tests.py 20: verify svn:needs-lock behavior with revert
>>
>> FAIL: lock_tests.py 24: lock and unlock a file with an URI-unsafe name
>>
>> FAIL: lock_tests.py 27: commit file with xml-unsafe name and release lock
>>
>> FAIL: lock_tests.py 34: unlock file locked by other user
>>
>> FAIL: depth_tests.py 19: diff at various depths in non-infinity wc
>>
>> FAIL: depth_tests.py 24: status -u at various depths in non-infinity wc
>
> DJ,
>
> Hmmm, I wonder if some of my recent changes to the test suite (r35093,
> r35083) are causing this. I can't replicate on my box. What version
> of Python does your buildbot use? And do you run the tests in
> parallel?

Some added speculation from IRC:

[08:36] <hwright> interesting failures on the windows buildbot
[08:36] <hwright> svn.exe ci -m ""
"svn-test-work\working_copies\basic_tests-45\iota" ...
[08:36] <hwright> svn: The log message is a pathname (was -F intended?); use
'--force-log' to override
[08:36] <hwright> it appears that windows no longer likes the empty log
messages being passed on the command line
[08:39] <julianf> There was some change to the "popen" / Python sub-process
code recently. Maybe that's stripping empty args accidentally.
[08:40] <hwright> possibly. It doesn't fail on *nix
[08:50] <cmpilato> julianf: that makes sense.
[08:50] <cmpilato> especially if we're flatting out command-line arguments to a
string for execution.

-Hyrum

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1014074
Received on 2009-01-09 18:22:57 CET

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