[New-bugs-announce] [issue10798] test_concurrent_futures fails on FreeBSD

Martin v. Löwis report at bugs.python.org
Thu Dec 30 21:14:14 CET 2010

New submission from Martin v. Löwis <martin at v.loewis.de>:

This is similar to #10348, but has a different scope; the attached patch disables the ProcessPoolExecutor if the system has too few POSIX semaphores.

To keep support for the ThreadPoolExecutor, I had the test cases stop using multiprocessing.Event in the threaded test cases. Unfortunately, this had two side effect that I think indicate a bug elsewhere: 

1. ThreadPoolWaitTests.test_all_completed_some_already_completed hangs
2. (sometimes) ThreadPoolWaitTests.test_first_exception fails:

    self.assertEqual(set([future1, future2]), finished)
AssertionError: Items in the first set but not the second:
<Future at 0x1851ad0 state=running>

I haven't been able to determine yet why it hangs. If the hanging test is disabled, the tests pass on both Linux and FreeBSD 7.3.

files: fbsd.diff
keywords: patch
messages: 124933
nosy: bquinlan, loewis
priority: normal
severity: normal
status: open
title: test_concurrent_futures fails on FreeBSD
Added file: http://bugs.python.org/file20198/fbsd.diff

Python tracker <report at bugs.python.org>

More information about the New-bugs-announce mailing list