[issue10798] test_concurrent_futures fails on FreeBSD
Mark Lawrence added the comment: Is it safe to assume that this test problem was resolved long ago? -- nosy: +BreamoreBoy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10798 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10798] test_concurrent_futures fails on FreeBSD
Changes by STINNER Victor victor.stin...@gmail.com: -- resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10798 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10798] test_concurrent_futures fails on FreeBSD
STINNER Victor victor.stin...@haypocalc.com added the comment: test_multiprocessing is still failing with OSError: [Errno 23] Too many open files in system on x86 FreeBSD 7.2 3.x: http://www.python.org/dev/buildbot/builders/x86%20FreeBSD%207.2%203.x/builds/1396/steps/test/logs/stdio I don't know the maximum number of POSIX semaphores on this buildbot. -- nosy: +haypo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10798 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10798] test_concurrent_futures fails on FreeBSD
Martin v. Löwis mar...@v.loewis.de added the comment: Interesting. I wonder whether a reboot of the system would help (as it may have old semaphores hanging around). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10798 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10798] test_concurrent_futures fails on FreeBSD
Brian Quinlan br...@sweetapp.com added the comment: Martin, Could you commit this patch if you think that it is the right thing? I'm going to be restructuring the tests and don't want you to get caught in merge hell. Cheers, Brian -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10798 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10798] test_concurrent_futures fails on FreeBSD
Martin v. Löwis mar...@v.loewis.de added the comment: Is this really the time for restructuring tests? I think such activity should wait until after the 3.2 release. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10798 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10798] test_concurrent_futures fails on FreeBSD
Brian Quinlan br...@sweetapp.com added the comment: The tests are currently flaky on Windows and I'd like to fix that before the release. But I don't have the bandwidth to debug the Call() abstraction used in the tests before 3.2 RC1. You can see the test change here: http://svn.python.org/view/python/branches/py3k-futures-on-windows/Lib/test/test_concurrent_futures.py?r1=87484r2=87652 So far it is passing on all the platforms that I've tested it on (Mac OS X, Ubuntu and Windows 7). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10798 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10798] test_concurrent_futures fails on FreeBSD
Martin v. Löwis mar...@v.loewis.de added the comment: Thanks for the review, committed as r87665. Fixing flaky tests is fine, of course. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10798 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10798] test_concurrent_futures fails on FreeBSD
Martin v. Löwis mar...@v.loewis.de added the comment: Follow-up: I have disabled test_all_completed_some_already_completed in r87667, as I couldn't figure out why it hangs. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10798 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10798] test_concurrent_futures fails on FreeBSD
New submission from Martin v. Löwis mar...@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 rep...@bugs.python.org http://bugs.python.org/issue10798 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
