New issue
Advanced search Search tips

Issue 888386 link

Starred by 1 user
Status: Fixed
Owner:
jbudorick@chromium.org
Closed: Sep 25
Cc:
kouhei@chromium.org
jbudorick@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

A zero-to-nonzero to 1.1% regression in rendering.mobile at 593336:593397

Project Member Reported by kouhei@google.com, Sep 24 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Sep 24 

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=888386

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


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

Android Nexus5 Perf
Android Nexus5X WebView Perf
android-nexus5x-perf

rendering.mobile - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Sep 24

Cc: jbudorick@chromium.org
Owner: jbudorick@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/16b51e2f640000

Use vpython and remove vendored pymock. by jbudorick@chromium.org
https://chromium.googlesource.com/catapult/+/23c67a511280f6dbc2a2bea849dd7eed5104809e
1.679 → No values

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

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks

Comment 4 by jbudorick@chromium.org, Sep 25

Status: Fixed (was: Assigned)
CL in question was reverted.
►

Sign in to add a comment