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

Re: Some failing tests

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Tue, 4 May 2010 23:43:11 +0300 (Jerusalem Daylight Time)

I saw it but kept silent because I had little to contribute. (I'm not
sure what's going on here, never saw a combination of failures resembling
it.) Some more comments below.

Johan Corveleyn wrote on Tue, 4 May 2010 at 22:29 +0200:
> Anyone?
>
> A simple answer like "this is obvious problem A, just search the list
> archives" or "it's not an obvious problem, you need to do some more
> digging" would already be quite helpful...
>
> Should this be relevant: this is a debug build (on Windows). Some dependencies:
> - APR 1.3.8
> - Neon 0.28.6 (I don't think that's relevant, since the tests are over ra_local)
> - Serf 0.3.0 (ditto)
>

(I tried serf on windows once. Don't remember if I succeeded.)

> Cheers,
> Johan
>
> On Sun, May 2, 2010 at 12:06 AM, Johan Corveleyn <jcorvel_at_gmail.com> wrote:
> > Hi devs,
> >
> > As I said in the mail thread about the misaligned blame output [1], I
> > wanted to get the test suite running first. However, after spending
> > some time with it, I still have 15 failing tests. I'd like that number
> > to be 0 before I start hacking. Or is it known/expected that certain
> > tests are currently failing on trunk?
> >

You can ask our buildbot/hudson instances:

<wayita> http://buildbot.subversion.org/buildbot/waterfall
<wayita> http://hudson.zones.apache.org/hudson/view/subversion/
<wayita> http://ci.apache.org/waterfall?show=slik-w2k3-x64-local&show=slik-w2k3-x64-ra

Normally trunk should be passing all tests.

> > I quite a newbie with this stuff, so any help is appreciated. Can
> > someone give me a hint or point me in the right direction?  I'm
> > running on Windows, built svn from trunk r940092, and this is the
> > command I used to run the tests:
> > python win-tests.py --verbose --cleanup --bin=$(TARGETDIR)\bin --debug -f fsfs
> >
> > The failing tests are:
> > FAIL:  dirent_uri-test.exe 37: test svn_dirent_condense_targets
> > FAIL:  depth_tests.py 5: update depth-immediates wc gets top file mod only
> > FAIL:  lock_tests.py 9: verify svn:needs-lock read-only behavior
> > FAIL:  log_tests.py 5: 'svn log -r COMMITTED' of dynamic/local WC rev
> > FAIL:  log_tests.py 17: test 'svn log -g' on a branching revision
> > FAIL:  log_tests.py 18: test 'svn log -g' on a non-branching revision
> > FAIL:  merge_tests.py 15: merge one file (issue #1150) using the -c option
> > FAIL:  merge_tests.py 20: merge into missing must not break working copy
> > FAIL:  merge_tests.py 25: merge prop change into deleted target
> > FAIL:  merge_tests.py 106: merge two successive edits to the same property
> > FAIL:  merge_tests.py 123: no self referential filtering on added path
> > FAIL:  merge_tests.py 140: merge into WC of deleted branch should work
> > FAIL:  mergeinfo_tests.py 7: test svn mergeinfo -R
> > FAIL:  update_tests.py 34: update handles obstructing paths scheduled for add
> > FAIL:  update_tests.py 47: tree conflicts 1.2: tree del, leaf del on update
> >
> > Some excerpts from tests.log:
> > ====
> > ..\..\..\subversion\tests\libsvn_subr\dirent_uri-test.c:2420: (apr_err=125001)
> > ..\..\..\subversion\libsvn_subr\dirent_uri.c:1980: (apr_err=125001)
> > ..\..\..\subversion\libsvn_subr\dirent_uri.c:1651: (apr_err=125001)
> > svn_tests: Couldn't determine absolute path of 'D:\dir'
> > ..\..\..\subversion\libsvn_subr\dirent_uri.c:1651: (apr_err=20024)
> > svn_tests: The given path is misformatted or contained invalid characters
> > FAIL:  dirent_uri-test.exe 37: test svn_dirent_condense_targets
> > ====
> >

Hmm. Longshot, but do you *have* a D: drive? (I don't know how APR
works with paths on non-existent drives.)

> > ====
> > ERROR:  load failed; did not see revision 1
> > EXCEPTION: SVNRepositoryCopyFailure
> > FAIL:  depth_tests.py 5: update depth-immediates wc gets top file mod only
> > ====
> >

For me, this usually "out of disk space". But you passed --cleanup...

This seems to be part of the pre-test code that initializes a blank
repository for that test to work on. (i.e., it's not an issue specific
to depth_tests 5)

> > ====
> > svn: Can't open file
> > 'C:\research\svn\client_build\svn_trunk\Debug\subversion\tests\cmdline\svn-test-work\repositories\log_tests-5\db\transactions\7-7.txn\next-ids':
> > The requested operation cannot be performed on a file with a
> > user-mapped section open.
> > ====
> >

Don't know.

> >
> > [1] http://svn.haxx.se/dev/archive-2010-04/0463.shtml
> >
> > Cheers,
> > --
> > Johan
> >
>
Received on 2010-05-04 22:43:04 CEST

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