New issue
Advanced search Search tips

Issue 650237 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Sep 2016
Cc:
jinho.b...@samsung.com
fdoray@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

4.1%-4.8% regression in speedometer at 420031:420071

Project Member Reported by hablich@chromium.org, Sep 26 2016 
See the link to graphs below.
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Sep 26 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@420030  520.651  10.8632  18  good
chromium@420051  513.152  12.0234  18  bad

Bisect job ran on: linux_perf_bisect
Bug ID: 650237

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests speedometer
Test Metric: jQuery-TodoMVC/jQuery-TodoMVC
Relative Change: 0.30%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/linux_perf_bisect/builds/6726
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9000456765091883552


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

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

Cc: jinho.b...@samsung.com
Owner: jinho.b...@samsung.com

=== Auto-CCing suspected CL author jinho.bang@samsung.com ===

Hi jinho.bang@samsung.com, 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 : PaymentRequest: Make the PaymentResponse interface serializable.
Author  : jinho.bang
Commit description:
  
Related spec change:
  https://github.com/w3c/browser-payment-api/pull/252

BUG= 648238 

Review-Url: https://codereview.chromium.org/2349133002
Cr-Commit-Position: refs/heads/master@{#420044}
Commit  : 6a3cc7f4a4b8d30e4f9b6f305a279fa3853b24b9
Date    : Wed Sep 21 14:07:55 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@420043  482.301  10.3031  18  good
chromium@420044  473.642  10.8497  18  bad    <--
chromium@420045  469.258  10.5906  18  bad
chromium@420047  471.368  9.56984  12  bad
chromium@420051  469.28   7.82977  12  bad

Bisect job ran on: linux_perf_bisect
Bug ID: 650237

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests speedometer
Test Metric: jQuery-TodoMVC/jQuery-TodoMVC
Relative Change: 2.87%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/linux_perf_bisect/builds/6725
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9000456793606975616


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

| 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 7 by 42576172...@developer.gserviceaccount.com, Sep 26 2016

Cc: fdoray@chromium.org
Owner: fdoray@chromium.org

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

Hi fdoray@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 : Delete MessageLoop::PostTask/PostDelayedTask/DeleteSoon/ReleaseSoon.
Author  : fdoray
Commit description:
  
These methods are deprecated and are no longer used in Chrome. To post
a task to a MessageLoop, developers should use its TaskRunner:

s/MessageLoop::current()->PostTask/ThreadTaskRunnerHandle::Get()->PostTask/
s/MessageLoop::current()->PostDelayedTask/ThreadTaskRunnerHandle::Get()->PostDelayedTask/
s/MessageLoop::current()->DeleteSoon/ThreadTaskRunnerHandle::Get()->DeleteSoon/
s/MessageLoop::current()->ReleaseSoon/ThreadTaskRunnerHandle::Get()->ReleaseSoon/

s/message_loop->PostTask/message_loop->task_runner()->PostTask/
s/message_loop->PostDelayedTask/message_loop->task_runner()->PostDelayedTask/
s/message_loop->DeleteSoon/message_loop->task_runner()->DeleteSoon/
s/message_loop->ReleaseSoon/message_loop->task_runner()->ReleaseSoon/

BUG= 616447 

Review-Url: https://codereview.chromium.org/2354053002
Cr-Commit-Position: refs/heads/master@{#420071}
Commit  : f8f41410b8ae7ace0ed51191668451ab40689233
Date    : Wed Sep 21 15:47:54 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@420043  737.58   8.58777  18  good
chromium@420057  742.912  10.7353  12  good
chromium@420064  744.922  4.49673  5   good
chromium@420068  737.896  9.76563  18  good
chromium@420070  739.426  7.36537  18  good
chromium@420071  731.156  6.79797  18  bad    <--

Bisect job ran on: win_x64_perf_bisect
Bug ID: 650237

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests speedometer
Test Metric: AngularJS-TodoMVC/AngularJS-TodoMVC
Relative Change: 1.05%
Score: 95.0

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


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

| 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 8 by fdoray@chromium.org, Sep 26 2016

Owner: ----
Status: Untriaged (was: Assigned)
Can't be caused by https://codereview.chromium.org/2354053002 This CL deleted unused code.

More likely to be caused by a v8 or blink change.
Project Member

Comment 10 by 42576172...@developer.gserviceaccount.com, Sep 28 2016 


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


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@420100  735.439  8.49383  5  bad

Bisect job ran on: win_x64_perf_bisect
Bug ID: 650237

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests speedometer
Test Metric: AngularJS-TodoMVC/AngularJS-TodoMVC
Relative Change: None
Score: 0

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


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

| 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 12 by 42576172...@developer.gserviceaccount.com, Sep 28 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@420043  738.088  9.70381  18  good
chromium@420071  735.462  8.90525  18  bad

Bisect job ran on: win_x64_perf_bisect
Bug ID: 650237

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests speedometer
Test Metric: AngularJS-TodoMVC/AngularJS-TodoMVC
Relative Change: 0.76%
Score: 0

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


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

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

Status: WontFix (was: Untriaged)
►

Sign in to add a comment