garbo task timeout should be dynamic
Bug #758574 reported by
Stuart Bishop
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Stuart Bishop |
Bug Description
The default garbo timeout is static for all tasks. A better approach is to calculate the task timeout based on the remaining number of tasks to run, the number of concurrent threads, and the time remaining before the script timeout.
Changed in launchpad: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Stuart Bishop (stub) |
status: | Triaged → In Progress |
Changed in launchpad: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fixed in stable r12809 <http:// bazaar. launchpad. net/~launchpad- pqm/launchpad/ stable/ revision/ 12809>.