New issue
Advanced search Search tips

Issue 599508 link

Starred by 0 users

Issue metadata

Status: WontFix
Owner:
Closed: Apr 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

10.3% improvement in thread_times.key_silk_cases at 382797:382807

Project Member Reported by rsch...@chromium.org, Mar 31 2016

Issue description

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

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


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

android-nexus5
Project Member

Comment 2 by 42576172...@developer.gserviceaccount.com, Mar 31 2016

Cc: yukishiino@chromium.org
Owner: yukishiino@chromium.org

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

Hi yukishiino@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 : Fixes cc_blink_unittests in a better way.
Author  : yukishiino
Commit description:
  
This is a better version of the fix of
http://crrev.com/1737873002

We should add "blink_for_unittests" to "cc_blink_unittests" rather than "cc_blink".

BUG= 589949 
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel

Review URL: https://codereview.chromium.org/1820903005

Cr-Commit-Position: refs/heads/master@{#382800}
Commit  : 22c03d9a0b8e15c7018b8b02225a0fe34b73e850
Date    : Wed Mar 23 06:42:01 2016


===== TESTED REVISIONS =====
Revision                Mean Value  Std. Dev.   Num Values  Good?
chromium@382796         20.153391   1.122967    12          good
chromium@382799         20.456491   0.840801    8           good
chromium@382800         18.335493   0.896652    5           bad         <-
chromium@382801         16.352926   0.82997     5           bad
chromium@382802         17.976814   1.750204    8           bad
chromium@382807         17.21158    0.729937    8           bad

Bisect job ran on: android_nexus5_perf_bisect
Bug ID: 599508

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --also-run-disabled-tests thread_times.key_silk_cases
Test Metric: thread_total_all_cpu_time_per_frame/thread_total_all_cpu_time_per_frame
Relative Change: 14.95%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/3535
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9016659293032362128


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

| 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!
Status: WontFix (was: Assigned)
This is an improvement, right?  Then, I close the issue as WontFix.

Sign in to add a comment