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

Vincent Ladeuil v.ladeuil+lp at free.fr
Wed Nov 19 18:24:40 GMT 2008


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

    Berny> Vincent wrote:
    >> - I'm able to reproduce the 'Too many open files'.
    >> - I don't get the "diff: illegal option" (because I use GNU
    Berny> diff-2.8.1)
    >> - I do get the
    >> 
    Berny> blackbox.test_remove.TestRemove.test_remove_changed_files_from_child_dir
    >> failure.
    >> 
    >> *and* this is also true with python-2.5.2.
    >> 
    >> Interrupting the selftest and using pfiles <pid> reveals that in
    >> fact the open files are sockets...
    >> 
    >> I have yet to understand why this happens on Solaris and not on
    >> Linux but it means that only selftest is concerned by the problem
    >> and not should not have consequences when using bzr itself.
    >> 
    >> I'll run the test suite by parts to check which tests are really
    >> failing and keep you informed, but the important result is that
    >> you should be safe using bzr.

    Berny> great - that you can reproduce it, not that the errors exist ;-)

;)

    Berny> I also saw many sockets with pfiles <pid>. And there also many
    Berny> lwps (/proc/<pid>/lwp/*). I guess the threads are communicating
    Berny> via sockets.

Yes, most of the client/server tests do that.

    Berny> BTW: can you really open the number of files shown
    Berny> with ulimit?  I can only open 255 ;-(

Check that you can are allowed to raise your limits:

ulimit -H -a
ulimit -S -a

Your admins may have set the hard limit at 256 and in that case
you can't override that with the soft limit.

    Vincent




More information about the bazaar mailing list