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

Issue 599507 link

Starred by 0 users

Issue metadata

Status: Duplicate
Merged: issue 597648
Owner:
Last visit > 30 days ago
Closed: Mar 2016
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=599507

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

Mergedinto: 597648
Status: Duplicate (was: Assigned)

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


===== SUSPECTED CL(s) =====
Subject : Handling transition animation between non-interpolable values.
Author  : abhishek.ka
Commit description:
  
In current transition animations, for any lengthsize css property
irrespective of interpolable values animation does start.
This patch will check whether the values are interpolable and decides
as follows:
i) If values are interpoable, start animation,
ii) else, hard set the respective length property to the element .
BUG= 513127 

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

Cr-Commit-Position: refs/heads/master@{#382801}
Commit  : 4d344058522e01d85162fcd1a9e5f4b747db9383
Date    : Wed Mar 23 06:48:44 2016


===== TESTED REVISIONS =====
Revision                Mean Value  Std. Dev.   Num Values  Good?
chromium@382796         23.515357   0.191995    5           good
chromium@382799         23.366571   0.219035    5           good
chromium@382800         23.701761   0.31772     5           good
chromium@382801         21.225261   0.28442     5           bad         <-
chromium@382802         21.199661   0.120672    5           bad
chromium@382807         21.106578   0.11794     5           bad

Bisect job ran on: android_nexus5_perf_bisect
Bug ID: 599507

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: 10.24%
Score: 99.9

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


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

| 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!

Sign in to add a comment