garbo task timeout should be dynamic

Bug #758574 reported by Stuart Bishop on 2011-04-12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
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.

Stuart Bishop (stub) on 2011-04-12
Changed in launchpad:
status: New → Triaged
importance: Undecided → High
assignee: nobody → Stuart Bishop (stub)
status: Triaged → In Progress
Launchpad QA Bot (lpqabot) wrote :
Changed in launchpad:
milestone: none → 11.05
tags: added: qa-needstesting
Changed in launchpad:
status: In Progress → Fix Committed
Robert Collins (lifeless) wrote :

Garbo on qastaging still runs

tags: added: qa-ok
removed: qa-needstesting
Curtis Hovey (sinzui) on 2011-05-06
Changed in launchpad:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers