On 27.10.2013 03:36, Branko Čibej wrote: > I'm getting really weird failures in depth-test.py on Mac OS. I noticed > it first in my trunk working copy (out-of-source build); a test was > asserting in libsvn_subr/sqlite.c:856 (i.e., a statement was not > properly reset). I couldn't find the reason, but since I had local > modifications that shouldn't have affected that part of the code, I was > worried. > > I checked out another copy of trunk and transferred the local mods over, > one file at a time, recompiling and re-running the test each time ... > the test passed. Re-ran whole tests, all tests passed again. Tried the > same with an out-of-trree build with the same configuration as the > original build ... the test still passed. > > Then I ran /all/ the tests -- and depth-test.py failed, but a > /different/ test this time. I thought, well, that's weird; so I cleaned > out svn-test-work and ran just depth-test.py ... and it failed again and > keeps failing. > > I'm a bit at a loss now. Any ideas? Before you ask: valgrind is not > reliable on the Mac.
Well, the failure is definitely real. I just Built Subversion on a completely fresh Mac Mini, without homebrew etc. -- just the latest autoconf and libtool. The same test fails as before. I'm going to do some bisecting to try to find the commit that caused this. -- Brane -- Branko Čibej | Director of Subversion WANdisco // Non-Stop Data e. [email protected]
