Issue metadata
Sign in to add a comment
|
Pinpoint shows improvement, Dashboard shows regression, whaaaa? |
||||||||||||||||||||
Issue descriptionNot sure what's going on here. The issue is in bug 893883: 1. On the dashboard (https://chromeperf.appspot.com/group_report?bug_id=893883), we can clearly see a regression in cpu_time_percentage_avg. 2. However, when Pinpoint is used to bisect, it says there's no problem. In fact, it shows the exact opposite (https://pinpoint-dot-chromeperf.appspot.com/job/1394246ce40000): the "after" measurement is 69.3% and the "before" measurement is 79.1%. So, this is actually NOT a regression, but an improvement? I'm so confused.
,
Oct 11
,
Oct 11
,
Oct 11
,
Oct 11
,
Oct 15
The NextAction date has arrived: 2018-10-15
,
Oct 18
I think the Pinpoint job at https://pinpoint-dot-chromeperf.appspot.com/job/1394246ce40000 did reproduce the regression as expected. However, because of issue 894529, it did not run enough repeats to be sure of the regression. I'll try re-running it.
,
Oct 25
,
Jan 11
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by m...@chromium.org
, Oct 11