Message124933
| Author |
loewis |
| Recipients |
bquinlan, loewis |
| Date |
2010年12月30日.20:14:02 |
| SpamBayes Score |
1.252906e-08 |
| Marked as misclassified |
No |
| Message-id |
<1293740054.42.0.931376139757.issue10798@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
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. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2010年12月30日 20:14:14 | loewis | set | recipients:
+ loewis, bquinlan |
| 2010年12月30日 20:14:14 | loewis | set | messageid: <1293740054.42.0.931376139757.issue10798@psf.upfronthosting.co.za> |
| 2010年12月30日 20:14:04 | loewis | link | issue10798 messages |
| 2010年12月30日 20:14:04 | loewis | create |
|