Closed
Bug 1087915
Opened 10 years ago
Closed 9 years ago
Pending jobs shouldn't be included in ETA prediction
Categories
(Tree Management :: Treeherder, defect, P3)
Tree Management
Treeherder
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1096605
People
(Reporter: emorley, Unassigned)
Details
(Keywords: regression)
20:55 NeilAway is it known that pending jobs can show as overdue? 20:56 camd NeilAway: do you have an example of a job I could look at? 21:01 NeilAway camd: 8e21737b6ff7 21:01 camd NeilAway: is that mozilla-inbound? 21:03 NeilAway camd: try 21:06 camd NeilAway: yeah, I think that can happen when the machines are quite busy. We do our best to predict how soon a job will complete based on past jobs of the same type. But sometimes it can take a long time for a job to start running if the machine load is high. 21:07 camd that being said, if this seems like it's off-base, then please do file a bug and we'll take a look at it. :) 21:09 NeilAway camd: well, surely you should only start predicting the completion time once the job has actually started? 21:13 camd NeilAway: I *think* the dev on that had tried to predict based on the time it took a pending job of that type to get all the way through to completion. I'd have to double-check. 21:19 camd NeilAway: yeah, it looks like he calculates an average based on the time, which will include the time to start. But that time can vary a fair bit depending on infrastructure load.
Reporter | ||
Updated•10 years ago
|
No longer blocks: treeherder-dev-transition
Keywords: regression
Reporter | ||
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•