New issue
Advanced search Search tips

Issue 625456 link

Starred by 2 users
Status: WontFix
Owner:
qyears...@chromium.org
Closed: Jul 2016
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

15.3% regression in blink_perf.bindings at 402983:403026

Project Member Reported by qyears...@chromium.org, Jul 3 2016 
See the link to graphs below.

Comment 1 by qyears...@chromium.org, Jul 3 2016 

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=625456

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


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

linux-release
Project Member

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


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


===== SUSPECTED CL(s) =====
Subject : Add the authenticate screen for the quick unlock settings.
Author  : jdufault
Commit description:
  
The authenticate screen verifies the user's account password, since the quick
unlock settings control how the device is unlocked from the lock screen after
the user has signed in.

This also adds the entry-point for quick unlock settings to the people page.

The authenticate screen is available from the /quickUnlock/authenticate
endpoint.

BUG= 603217 
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:closure_compilation

Review-Url: https://codereview.chromium.org/2091143002
Cr-Commit-Position: refs/heads/master@{#402984}
Commit  : 7982a71bf7df88606e941c00cbedf62a10077a38
Date    : Wed Jun 29 23:16:44 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@402982  246.074  3.48038  27  good
chromium@402983  246.063  4.41844  12  good
chromium@402984  247.932  3.86608  12  bad    <--
chromium@402985  248.239  3.16463  12  bad
chromium@402988  250.603  6.00229  27  bad
chromium@402993  252.668  5.2997   18  bad
chromium@403004  251.681  3.18016  8   bad
chromium@403026  258.784  2.88145  5   bad

Bisect job ran on: linux_perf_bisect
Bug ID: 625456

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests blink_perf.bindings
Test Metric: node-list-access/node-list-access
Relative Change: 5.48%
Score: 80.0

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


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

| 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 3 by qyears...@chromium.org, Jul 3 2016 

The above result doesn't look too convincing; starting another bisect job.
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Jul 4 2016 


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


===== SUSPECTED CL(s) =====
Subject : Add the authenticate screen for the quick unlock settings.
Author  : jdufault
Commit description:
  
The authenticate screen verifies the user's account password, since the quick
unlock settings control how the device is unlocked from the lock screen after
the user has signed in.

This also adds the entry-point for quick unlock settings to the people page.

The authenticate screen is available from the /quickUnlock/authenticate
endpoint.

BUG= 603217 
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:closure_compilation

Review-Url: https://codereview.chromium.org/2091143002
Cr-Commit-Position: refs/heads/master@{#402984}
Commit  : 7982a71bf7df88606e941c00cbedf62a10077a38
Date    : Wed Jun 29 23:16:44 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@402982  231.726  5.23148  93  good
chromium@402983  232.438  3.68556  62  good
chromium@402984  232.927  5.22441  93  bad    <--
chromium@402985  234.568  3.11111  62  bad
chromium@402988  237.448  5.01727  18  bad
chromium@402993  238.228  4.26229  18  bad
chromium@403004  237.823  5.86973  12  bad
chromium@403026  238.659  5.12763  18  bad

Bisect job ran on: linux_perf_bisect
Bug ID: 625456

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests blink_perf.bindings
Test Metric: node-list-access/node-list-access
Relative Change: 1.95%
Score: 80.0

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


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

| 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 5 by qyears...@chromium.org, Jul 7 2016

Status: WontFix (was: Assigned)
Appears recovered at the latest results.
Project Member

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


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


===== SUSPECTED CL(s) =====
Subject : Add the authenticate screen for the quick unlock settings.
Author  : jdufault
Commit description:
  
The authenticate screen verifies the user's account password, since the quick
unlock settings control how the device is unlocked from the lock screen after
the user has signed in.

This also adds the entry-point for quick unlock settings to the people page.

The authenticate screen is available from the /quickUnlock/authenticate
endpoint.

BUG= 603217 
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:closure_compilation

Review-Url: https://codereview.chromium.org/2091143002
Cr-Commit-Position: refs/heads/master@{#402984}
Commit  : 7982a71bf7df88606e941c00cbedf62a10077a38
Date    : Wed Jun 29 23:16:44 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev   N    Good?
chromium@402982  231.558  4.40803   140  good
chromium@402983  232.374  3.91713   140  good
chromium@402984  232.516  6.25243   93   bad    <--
chromium@402985  233.988  4.40489   18   bad
chromium@402988  236.893  2.60684   5    bad
chromium@402993  240.019  0.612367  5    bad
chromium@403004  237.143  5.09262   8    bad
chromium@403026  240.888  5.04392   8    bad

Bisect job ran on: linux_perf_bisect
Bug ID: 625456

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests blink_perf.bindings
Test Metric: node-list-access/node-list-access
Relative Change: 4.18%
Score: 0.0

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


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

| 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