New issue
Advanced search Search tips

Issue 629917 link

Starred by 2 users
Status: Duplicate
Merged: issue 629296
Owner:
dtapu...@chromium.org
Closed: Aug 2016
Cc:
dtapu...@chromium.org
tdres...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

147.8%-1341.2% regression in smoothness.top_25_smooth at 405230:405479

Project Member Reported by majidvp@google.com, Jul 20 2016 
May be a duplicate of 629296.
Project Member

Comment 3 by sheriffbot@chromium.org, Jul 21 2016

Labels: Hotlist-Google
Project Member

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

Bisect failed: Unknown
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, Jul 29 2016 


===== BISECT JOB RESULTS =====
Status: failed


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@405407  11.7824  1.798    5  good
chromium@405479  166.53   11.5596  5  bad

Bisect job ran on: win_x64_perf_bisect
Bug ID: 629917

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.top_25_smooth
Test Metric: mean_input_event_latency/http___answers.yahoo.com
Relative Change: 1316.05%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_x64_perf_bisect/builds/1342
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9006396435152431552


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

| 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 10 by 42576172...@developer.gserviceaccount.com, Jul 29 2016 

Bisect failed: Unknown
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, Jul 29 2016 


===== BISECT JOB RESULTS =====
Status: failed


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@405407  11.7824  1.798    5  good
chromium@405479  166.53   11.5596  5  bad

Bisect job ran on: win_x64_perf_bisect
Bug ID: 629917

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.top_25_smooth
Test Metric: mean_input_event_latency/http___answers.yahoo.com
Relative Change: 1316.05%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_x64_perf_bisect/builds/1342
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9006396435152431552


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

| 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 16 by 42576172...@developer.gserviceaccount.com, Aug 6 2016 


===== BISECT JOB RESULTS =====
Status: failed


===== TESTED REVISIONS =====
Revision         Mean     Std Dev   N  Good?
chromium@405409  9.7084   0.391064  5  good
chromium@405432  82.5434  6.23695   5  bad

Bisect job ran on: winx64nvidia_perf_bisect
Bug ID: 629917

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.top_25_smooth
Test Metric: mean_input_event_latency/ESPN
Relative Change: 767.53%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64nvidia_perf_bisect/builds/1758
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005837449586284352


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

| 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 18 by 42576172...@developer.gserviceaccount.com, Aug 6 2016 


===== BISECT JOB RESULTS =====
Status: failed


===== TESTED REVISIONS =====
Revision         Mean     Std Dev   N  Good?
chromium@405409  9.6532   0.274286  5  good
chromium@405432  84.5558  14.847    5  bad

Bisect job ran on: winx64nvidia_perf_bisect
Bug ID: 629917

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.top_25_smooth
Test Metric: mean_input_event_latency/ESPN
Relative Change: 717.54%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64nvidia_perf_bisect/builds/1759
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9006396435152431552


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

| 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 19 by 42576172...@developer.gserviceaccount.com, Aug 6 2016

Cc: dtapu...@chromium.org
Owner: dtapu...@chromium.org

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

Hi dtapuska@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 : Revert of Enable PassiveDocumentEventListeners on waterfall. (patchset #2 id:20001 of https://codereview.chromium.org/2119403002/ )
Author  : dtapuska
Commit description:
  
Reason for revert:
Revert this for now. We are seeing cc:scheduler changes as a result of this and we need to understand them better and I'm not going to be in the office the next two days.

Original issue's description:
> Enable PassiveDocumentEventListeners on waterfall.
>
> Enable passive document event listeners finch experimentl on waterfall.
>
> BUG= 625675 
> R=rkaplow@chromium.org
>
> Committed: https://crrev.com/19233086ad7e2363e7e1d14582dc6a5428816169
> Cr-Commit-Position: refs/heads/master@{#404351}

TBR=rkaplow@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG= 625675 

Review-Url: https://codereview.chromium.org/2149673002
Cr-Commit-Position: refs/heads/master@{#405240}
Commit  : 38e3bf349d518922038c1918bd76480bd2924fc4
Date    : Wed Jul 13 19:55:06 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@405229  14.182   3.92596  5  good
chromium@405236  9.5902   3.1215   5  good
chromium@405239  8.7014   2.0793   5  good
chromium@405240  54.7424  14.7186  5  bad    <--
chromium@405241  51.1546  9.23554  5  bad
chromium@405242  67.0084  13.7827  5  bad
chromium@405255  53.4824  10.065   5  bad
chromium@405280  72.1912  14.3112  5  bad
chromium@405331  56.4352  14.9633  5  bad
chromium@405432  51.6752  8.03032  5  bad

Bisect job ran on: android_nexus9_perf_bisect
Bug ID: 629917

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.top_25_smooth
Test Metric: first_gesture_scroll_update_latency/https___mail.google.com_mail_
Relative Change: 264.37%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/1987
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005130125963676800


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

| 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 20 by dtapu...@chromium.org, Aug 8 2016 

The mean_input_event_latency graphs are all missing the gesture scroll begin/update/end components causing the latency to increase because there aren't many samples afterwards.

Comment 21 by dtapu...@chromium.org, Aug 8 2016

Cc: tdres...@chromium.org
One of the mean_input_latency traces reports:

At 3483567110, no slice named InputLatency::TouchMove with id=0xe00000006 was open.
Project Member

Comment 23 by 42576172...@developer.gserviceaccount.com, Aug 9 2016 


===== BISECT JOB RESULTS =====
Status: failed


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@405407  13.113   1.33395  5  good
chromium@405479  172.881  12.523   6  bad

Bisect job ran on: win_x64_perf_bisect
Bug ID: 629917

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.top_25_smooth
Test Metric: mean_input_event_latency/http___answers.yahoo.com
Relative Change: 1177.82%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_x64_perf_bisect/builds/1396
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004799923797059920


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

| 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 25 by 42576172...@developer.gserviceaccount.com, Aug 9 2016 


===== BISECT JOB RESULTS =====
Status: failed


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@405407  13.113   1.33395  5  good
chromium@405479  172.881  12.523   6  bad

Bisect job ran on: win_x64_perf_bisect
Bug ID: 629917

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.top_25_smooth
Test Metric: mean_input_event_latency/http___answers.yahoo.com
Relative Change: 1177.82%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_x64_perf_bisect/builds/1396
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004799923797059920


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

| 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 27 by 42576172...@developer.gserviceaccount.com, Aug 10 2016

Mergedinto: 629296
Status: Duplicate (was: Assigned)

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


===== SUSPECTED CL(s) =====
Subject : Fix component-installer-controlled Flash path.
Author  : waffles
Commit description:
  
BUG=627959

Review-Url: https://codereview.chromium.org/2150573004
Cr-Commit-Position: refs/heads/master@{#405419}
Commit  : 3436cd4cbccb4c573185e2faefc248727e1baecb
Date    : Thu Jul 14 02:50:17 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev   N  Good?
chromium@405409  9.7764   0.330173  5  good
chromium@405415  9.5594   0.354103  5  good
chromium@405418  9.806    0.225491  5  good
chromium@405419  73.5574  28.5535   5  bad    <--
chromium@405420  74.9172  20.5769   5  bad
chromium@405432  78.4392  28.8647   5  bad

Bisect job ran on: winx64nvidia_perf_bisect
Bug ID: 629917

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.top_25_smooth
Test Metric: mean_input_event_latency/ESPN
Relative Change: 828.01%
Score: 99.5

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64nvidia_perf_bisect/builds/1801
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004799923797059920


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

| 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 28 by dtapu...@chromium.org, Sep 27 2016

Labels: Hotlist-Input-Dev
►

Sign in to add a comment