New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 884786 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Sep 18
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

6%-6.8% regression in media.mobile at 590797:590896

Project Member Reported by chcunningham@chromium.org, Sep 17

Issue description

Jump in android cpu_time_percentage_avg on two bots. Ref graph held steady.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=884786

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=bda9b8cf494105d8cb802752fdd3764e33437cba9647800eaba6bbd237157ce1


Bot(s) for this bug's original alert(s):

Android Nexus5 Perf
android-nexus5x-perf

media.mobile - Benchmark documentation link:
  None
Cc: fsam...@chromium.org
Owner: fsam...@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/166e5f4b640000

DelegatedFrameHostAndroid: Fix Screen Capture by fsamuel@chromium.org
https://chromium.googlesource.com/chromium/src/+/36be926f766fe3f0cb231123e4b9e6b087aa27e0
0.7582 → 0.808 (+0.04974)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Benchmark documentation link:
  None
Status: WontFix (was: Assigned)
Marking as won't fix. There was a bug that was probably making this test run faster than it should (it wasn't setting the device scale correctly).

Sign in to add a comment