AW: AW: bzr selftest (on solaris 10): too may open files

[Vincent Ladeuil]

>>>>> "Bernhard" == Voelker, Bernhard <bernhard.voelker at siemens.com> writes:

<snip/>

    Bernhard> Is python 2.4.4 supposed to work with bzr?

Yes. But the stable 2.4 version is 2.4.5, so may be you suffer
from a python bug. Is upgrading to 2.4.5 or even better to 2.5
an option in your case ?

    Bernhard> I'm not familiar with python, but could bzr call
    Bernhard> the garbage collector after each test?

No, we don't want to do that.

    Bernhard> (On the other side, this would taint the test
    Bernhard> because this is not done in normal code I
    Bernhard> guess...).

That's one reason yes, but it will also slow down the test suite
and may hide bugs.

Anyway, there has been numerous occasions where running the test
suite wasn't possible until some bugs, specific to the targeted
platform where fixed first and that 'too many open files' is
probably a red herring.

My suggestion would then be to try to run smaller parts of the
test suite to identify the first failing test, or just run the
test suite with the '-1' flag:

  bzr selftest -1

Or at least, tell us about the first test[s] reported as either
FAIL or ERROR.

Then try re-running that single test.

For example if you get: 

	ERROR: test_store.TestTransportStore.test_add_prefixed

Try running:

  bzr selftest -s bt.test_store.TestTransportStore.test_add_prefixed

and if it still fails, you will be able to see and send the
traceback. From there we may be able to make more educated guesses.

    Vincent