ProcessPool.callRemote Deferred sometimes fires with None instead of result
Bug #571334 reported by
Jean-Paul Calderone
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ampoule |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
This is a weird behavior I ran into when issuing a new job from an errback on an earlier job. The attached illustrates better than I can do in English. The expected result is to see a result of {}, though, since that is what the "Fast" command in the worker returns. Instead, the result is None.
Related branches
lp://staging/~cjwatson/ampoule/process-error-not-ready
On hold
for merging
into
lp://staging/ampoule
- dialtone: Pending requested
-
Diff: 44 lines (+13/-3)2 files modifiedampoule/pool.py (+1/-1)
ampoule/test/test_process.py (+12/-2)
To post a comment you must log in.
Another clue here is that the example program also logs an unhandled error. However, it seems to me that it is properly handling the error.