Closed
Bug 1517052
Opened 7 years ago
Closed 7 years ago
[raptor] Do not report power usage when raptor fails to report results
Categories
(Testing :: Raptor, enhancement, P1)
Testing
Raptor
Tracking
(firefox66 fixed)
RESOLVED
FIXED
mozilla66
| Tracking | Status | |
|---|---|---|
| firefox66 | --- | fixed |
People
(Reporter: bc, Assigned: rwood)
References
Details
Attachments
(1 file)
The power tests show bimodal behavior with higher energy usage when raptor fails to report results. See Bug 1499253. I don't believe that these energy usage values are useful when raptor fails and will make it difficult to determine improvements or regressions in energy usage.
We should not report energy PERFHERDER_DATA when raptor fails to report results.
rwood: Do you think you could take this? You know the results reporting in raptor much better than I do.
| Assignee | ||
Comment 1•7 years ago
|
||
Thanks :bc makes sense, yep I'll take this.
Assignee: nobody → rwood
Status: NEW → ASSIGNED
| Assignee | ||
Updated•7 years ago
|
Priority: -- → P1
| Assignee | ||
Comment 2•7 years ago
|
||
| Assignee | ||
Comment 3•7 years ago
|
||
| Assignee | ||
Comment 4•7 years ago
|
||
| Assignee | ||
Comment 5•7 years ago
|
||
(In reply to Robert Wood [:rwood] from comment #4)
> https://treeherder.mozilla.org/#/jobs?repo=try&revision=90c88eabe7cc96951bd1d4fdd20735955ece7997
In that try push ^ I temporarily reduced the Raptor speedometer geckoview timeout, to force the speedometer test to fail. Looks good - the power measurements were gathered successfully but not dumped to Perfherder since the actual speedometer test itself failed to complete.
| Assignee | ||
Comment 6•7 years ago
|
||
Pushed by rwood@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/7627e62b3833
[raptor] Do not report power usage when raptor fails to report results; r=jmaher
Comment 8•7 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
status-firefox66:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla66
You need to log in
before you can comment on or make changes to this bug.
Description
•