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

Issue 632653 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 632651
Owner:
Last visit > 30 days ago
Closed: Jul 2016
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

6%-17.9% regression in thread_times.tough_scrolling_cases at 408318:408338

Project Member Reported by alexclarke@chromium.org, Jul 29 2016

Issue description

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

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


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

chromium-rel-win7-dual
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jul 29 2016

Mergedinto: 632651
Status: Duplicate (was: Assigned)

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


===== SUSPECTED CL(s) =====
Subject : Try again to flip official win builders to GN.
Author  : dpranke
Commit description:
  
We believe we've fixed the remaining known issues w/ the upload/
signing scripts, so it's time to try again. This affects:

- chromium.perf
  - Win Builder
- official.desktop
  - win
  - win64
- official.desktop.continuous
  - win beta
  - win stable
  - win trunk
  - win64 trunk

(Though the beta and stable builders aren't actually affected and
won't be until they are on M54).

TBR=sebmarchand@chromium.org, brettw@chromium.org, brucedawson@chromium.org
BUG= 623659 

Review-Url: https://codereview.chromium.org/2187613004
Cr-Commit-Position: refs/heads/master@{#408318}
Commit  : e28fd5d84cebeb446e2c35cf6b766e35aa56ec5f
Date    : Thu Jul 28 02:44:20 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev   N  Good?
chromium@408317  25.699   0.162369  8  good
chromium@408318  27.108   0.597042  5  bad    <--
chromium@408319  26.5732  0.422163  5  bad
chromium@408320  26.9857  0.700268  8  bad
chromium@408322  26.5872  0.193807  5  bad
chromium@408328  26.7059  0.599159  8  bad
chromium@408338  26.6585  0.48146   5  bad

Bisect job ran on: win_perf_bisect
Bug ID: 632653

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests thread_times.tough_scrolling_cases
Test Metric: thread_total_all_cpu_time_per_frame/thread_total_all_cpu_time_per_frame
Relative Change: 3.70%
Score: 98.0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_perf_bisect/builds/6750
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005812415696867856


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

| 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