We had a windows build bustage that caused busted/failed builds around ~ 12 minutes after starting. Now with this fixed bustage new builds have information like for pgo builds: Windows XP pgo Build (B) 33 mins overdue, typically takes ~ 12 mins of course pgo builds never take 12 minutes :) so we maybe want to exclude failed builds into that eta calculation and only use completed/sucess builds
Yeah agree it doesn't take job state into account when it should. Bug 1228983 has this and a few other suggestions :-)
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1228983
You need to log in before you can comment on or make changes to this bug.