RetroSearch Browse

Wed Dec 29 21:04:11 CET 2010 · https://mail.python.org/pipermail/python-dev/2010-December/107102.html

On Wed, 29 Dec 2010 14:14:03 -0500
"R. David Murray" <rdmurray at bitdance.com> wrote:
> On Wed, 29 Dec 2010 12:58:55 -0500, Jesse Noller <jnoller at gmail.com> wrote:
> > The concurrent.futures tests should (like the multiprocessing test
> > suite) detect the lack of support and skip the tests on the broken
> > platforms. I'm sort of surprised FreeBSD support is still broken in
> > this way though (echoed by Philip) although it could be an issue on
> > that particular buildbot.
> 
> If I'm reading the issue correctly, it isn't that it doesn't work,
> it's that the concurrent.futures tests fail because they create more
> semaphores than the default FreeBSD install supports.

Doesn't it suggest a possible resource leak somewhere? Or do the
concurrent tests really rely on creating many semaphores? (as opposed
to say 5 or 10 of them)

Regards

Antoine.

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2010-December/107102.html below:

concurrent.futures doesn't work on BSD