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

Issue 657197 link

Starred by 2 users
Status: Duplicate
Merged: issue 651547
Owner: ----
Closed: Oct 2016
Cc:
█ jasontiller@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

53.9%-85.7% regression in smoothness.top_25_smooth at 421637:421734

Project Member Reported by jasontiller@chromium.org, Oct 18 2016 
Most of these metrics recovered, but I'm going to kick off a bisect for the two that didn't for verification.
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Oct 19 2016 

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_hdd_perf_bisect/builds/855
Failure reason: the build has failed.
Additional errors:
The metric was not found in the test output.
Either of the initial "good" or "bad" revisions failed to be tested or built.
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, Oct 19 2016 

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_hdd_perf_bisect/builds/856
Failure reason: the build has failed.
Additional errors:
The metric was not found in the test output.
Either of the initial "good" or "bad" revisions failed to be tested or built.
Project Member

Comment 7 by 42576172...@developer.gserviceaccount.com, Oct 19 2016 


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


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@421688  58.3107  5.84603  18  good
chromium@421703  56.2387  5.3305   18  bad

Bisect job ran on: mac_hdd_perf_bisect
Bug ID: 657197

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests smoothness.top_25_smooth
Test Metric: mean_input_event_latency/http___www.amazon.com
Relative Change: 1.13%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_hdd_perf_bisect/builds/854
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8998420640528453552


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

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

Comment 9 by 42576172...@developer.gserviceaccount.com, Oct 19 2016 

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_hdd_perf_bisect/builds/861
Failure reason: the build has failed.
Additional errors:
The metric was not found in the test output.
Either of the initial "good" or "bad" revisions failed to be tested or built.
Project Member

Comment 11 by 42576172...@developer.gserviceaccount.com, Oct 26 2016

Mergedinto: 651547
Status: Duplicate (was: Untriaged)

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


===== SUSPECTED CL(s) =====
Subject : Update fieldtrial_util To Handle Combined Fieldtrial Config Format
Author  : robliao
Commit description:
  
BUG=649363, 650705

Review-Url: https://codereview.chromium.org/2373843002
Cr-Commit-Position: refs/heads/master@{#421670}
Commit  : 8da8200a279fcafc4a7c68f2e6ef95f4d721bb3a
Date    : Wed Sep 28 22:51:09 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev   N  Good?
chromium@421550  12.329   1.29909   5  good
chromium@421650  13.514   1.88078   5  good
chromium@421663  12.4542  0.788628  5  good
chromium@421669  11.815   1.27545   5  good
chromium@421670  30.5514  4.71344   5  bad    <--
chromium@421671  29.7578  3.19339   5  bad
chromium@421672  28.274   0.702978  5  bad
chromium@421675  29.1898  3.42601   5  bad
chromium@421700  27.9162  2.06515   5  bad
chromium@421750  30.3128  4.27148   5  bad

Bisect job ran on: mac_hdd_perf_bisect
Bug ID: 657197

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=Blogger smoothness.top_25_smooth
Test Metric: mean_input_event_latency/Blogger
Relative Change: 145.87%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_hdd_perf_bisect/builds/864
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8997724131216771344


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

| 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