Gavin Baumanis wrote:
> I have finally managed to compile Subversion on my Mac - wahoo for me!
Great!
> It took 50 minutes to compile simply using ./configure;make;make
> install;
> Is this "about" normal? - not ever having compiled it before I have no
> point of reference for whether this is a long time or not.
I haven't tried it on a Mac but that sounds very long. It takes my
machine less than 5 minutes.
> The summary says that only 5 tests failed, but there are most
> certainly more than 5 failures listed.
> So why is there is a discrepancy, and which of these two outputs
> should I believe?
Ah, that's a bug in the test suite: all of your Python test files are
completely failing to run, and for each of those the test suite prints
"authz_tests.py [33/77].............FAILURE", but it doesn't count that
failure in the summary.
I'll post a patch to try to fix that.
> And while I do recall specific "test failures" mentioned at times
> within the dev mailing list;
> Is there a "protocol" to follow if you notice a test failure?
>
> I guess it is going to be an experience "thing" - but how do you know
> what test failures are important and which aren't?
> Or is it a case of they're all important?
They are all important. The project policy is for all tests to be
passing (or marked XFAIL etc) at all times. When there is a failure, it
is usually your local mods or your local set-up that are the problem.
Sometimes there are a few failures that are hard to debug and exist for
up to a few weeks, but we try hard to avoid that because it makes
everyone's life difficult because then they don't know whether failures
are their fault or not.
So you need to look for the cause of your failures. Start with either
the first C test that fails or the first Python test that fails,
depending on which you are more comfortable with debugging. For the
Python tests, look in "tests.log" which was created by running the test
suite, or run an individual test in "verbose" mode:
cd subversion/tests/cmdline
./authz_tests.py 1 --verbose
First, you should probably look through the output of "./configure" and
see if there were any failures or warnings there, because maybe part of
your build failed.
- Julian
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2415764
Received on 2009-11-09 13:22:58 CET