Closed
Bug 1123419
Opened 10 years ago
Closed 10 years ago
"ETA to completed" sometimes very inaccurate (Android x86, try)
Categories
(Tree Management :: Treeherder, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1096605
People
(Reporter: gbrown, Unassigned)
Details
The Android x86 "S4" test job seems to run in about 40 minutes and "ETA to completed" estimates on mozilla-inbound reflect that. However, in a try push - https://treeherder.mozilla.org/#/jobs?repo=try&revision=aadc3ecc0aa9 - I see
ETA to completed: 132 minutes
Duration: 31 minutes
I think I have seen this sort of gross over-estimate before, but can't recall specifics. If this isn't a known problem, I'll keep an eye out for this condition and report more examples here.
The ETA is calculated based on recent runs (on the current tree?), if I remember right. It also includes the time spent with the job pending, last I knew.
If those two things are still true, all of the time those tests spend pending on a low priority tree like try could probably really screw up the ETA.
Comment 2•10 years ago
|
||
There are a few issues with ETA at the moment - I think many are related, so I'm going to put them all in bug 1096605.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•