RetroSearch Browse

Wed Dec 29 16:01:38 CET 2010 · https://mail.python.org/pipermail/python-dev/2010-December/107087.html

Am 29.12.2010 14:17, schrieb Victor Stinner:
> Hi,
> 
> FreeBSD 7.2 3.x buildbot is red since some weeks (or months?) because of
> a concurrent.futures failure. The problem is that
> test_concurrent_futures uses many (multiprocessing) POSIX semaphores,
> whereas POSIX semaphores support in FreeBSD is recent and limited. We
> have to use SysV semaphores (ftok, semget, semop, semctl, ...) instead
> of POSIX semaphores (sem_open, sem_getvalue, sem_unlink, ...). See:
> 
>  * http://bugs.python.org/issue10348
>  * "Too many open files" errors on "x86 FreeBSD 7.2 3.x" buildbot
>    ^-- thread in python-dev opened last month
> 
> I would like to know if it should be considered as a release blocker.
> Georg Brandl said yes on IRC.

Under the condition that it is within reason to fix it before the
release.

Georg

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

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

concurrent.futures doesn't work on BSD