New issue
Advanced search Search tips

Issue 641281 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Aug 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

5% regression in speedometer at 414587:414626

Project Member Reported by nikolaos@chromium.org, Aug 26 2016

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=641281

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgvtqUqQoM


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

android-nexus7v2
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Aug 26 2016

Cc: finnur@chromium.org
Owner: finnur@chromium.org

=== Auto-CCing suspected CL author finnur@chromium.org ===

Hi finnur@chromium.org, the bisect results pointed to your CL below as possibly
causing a regression. Please have a look at this info and see whether
your CL be related.


===== BISECT JOB RESULTS =====
Status: completed


===== SUSPECTED CL(s) =====
Subject : Site Settings Desktop: Fix cookie data labelling for Indexed DBs.
Author  : finnur
Commit description:
  
BUG=640924,  614277 
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

Review-Url: https://codereview.chromium.org/2277213002
Cr-Commit-Position: refs/heads/master@{#414612}
Commit  : aafe66ab5cdbe2036354dd6304a1f517387bab47
Date    : Fri Aug 26 01:20:56 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@414586  8064.1   118.274  8   good
chromium@414606  8031.67  96.2135  12  good
chromium@414611  8065.65  93.679   41  good
chromium@414612  8156.78  124.972  18  bad    <--
chromium@414613  8119.77  111.566  41  bad
chromium@414614  8126.62  103.196  41  bad
chromium@414616  8130.73  106.183  41  bad
chromium@414626  8164.63  96.6491  8   bad

Bisect job ran on: android_nexus7_perf_bisect
Bug ID: 641281

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests speedometer
Test Metric: AngularJS-TodoMVC/AngularJS-TodoMVC
Relative Change: 2.16%
Score: 95.0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/3267
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9003280172933462768


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5893018188513280

| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Tests>AutoBisect.  Thank you!

Comment 4 by finnur@chromium.org, Aug 29 2016

Cc: -finnur@chromium.org
Labels: Sheriff-Chromium
Owner: ----
Status: Untriaged (was: Assigned)
Couple of problems with this bisect result:

1) The perf issue is on Android and my change is Desktop only.
2) My change is a single line change from fetching one string to another. It's hard to think of a less significant change in terms of performance impact.

Adding the Sheriff-Chromium label to ensure this gets triaged.
Status: WontFix (was: Untriaged)
This is probably a flake, then, I'm closing it.

Sign in to add a comment