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

Issue 631038 link

Starred by 2 users
Status: WontFix
Owner:
█ junov@chromium.org
Last visit > 30 days ago
Closed: Sep 2016
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

51% regression in blink_perf.canvas at 407211:407312

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

Comment 1 by primiano@chromium.org, Jul 25 2016 

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

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


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

win-zenbook
Project Member

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

Cc: dschuyler@chromium.org
Owner: dschuyler@chromium.org

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

Hi dschuyler@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 : [MD settings] close the side nav when navigating back/forward
Author  : dschuyler
Commit description:
  
This CL solves a problem with the side nav menu drawer staying open when
using the back/forward buttons. The drawer now closes when navigating
forward or back.

BUG= 623903 
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

Review-Url: https://codereview.chromium.org/2170223002
Cr-Commit-Position: refs/heads/master@{#407290}
Commit  : f2e8191e41dae27a051bc54271fbd971db1bfafd
Date    : Fri Jul 22 22:56:37 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev   N  Good?
chromium@407210  188.803  0.458184  5  good
chromium@407261  185.561  0.51958   5  good
chromium@407285  205.914  0.307217  5  good
chromium@407289  206.201  0.131735  5  good
chromium@407290  185.407  0.75007   5  bad    <--
chromium@407291  185.819  0.109417  5  bad
chromium@407293  186.195  0.256711  5  bad
chromium@407301  171.156  0.566123  5  bad
chromium@407312  169.255  0.12854   5  bad

Bisect job ran on: winx64_zen_perf_bisect
Bug ID: 631038

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests blink_perf.canvas
Test Metric: putImageData/putImageData
Relative Change: 10.35%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/297
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9006155711395410224


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

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


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


===== SUSPECTED CL(s) =====
Subject : Update WebGL2 conformance test expectations.
Author  : zmo
Commit description:
  
BUG=
TEST=webgl2_conformance
TBR=qiankun.miao@intel.com
NOTRY=true
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel

Review-Url: https://codereview.chromium.org/2177653005
Cr-Commit-Position: refs/heads/master@{#407301}
Commit  : edb7fd1c8cce0d3a342a467fab3837ecf10af7c7
Date    : Fri Jul 22 23:42:23 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@407210  184.601  5.58243  5  good
chromium@407261  180.671  6.5775   5  good
chromium@407285  198.9    10.2982  5  good
chromium@407293  181.75   3.83175  5  good
chromium@407297  183.593  3.5814   5  good
chromium@407299  179.149  14.7888  8  good
chromium@407300  179.966  13.3343  8  good
chromium@407301  148.13   29.3796  5  bad    <--
chromium@407312  165.013  5.67104  5  bad

Bisect job ran on: winx64_zen_perf_bisect
Bug ID: 631038

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests blink_perf.canvas
Test Metric: putImageData/putImageData
Relative Change: 10.61%
Score: 90.0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/298
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9006155696262754368


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

| 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 6 by primiano@chromium.org, Jul 26 2016

Cc: -dschuyler@chromium.org
Owner: primiano@chromium.org
https://codereview.chromium.org/2170223002 is clearly unrelated.
same for https://codereview.chromium.org/2177653005
Bisectbot, go home.
Project Member

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


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


===== SUSPECTED CL(s) =====
Subject : [MD settings] close the side nav when navigating back/forward
Author  : dschuyler
Commit description:
  
This CL solves a problem with the side nav menu drawer staying open when
using the back/forward buttons. The drawer now closes when navigating
forward or back.

BUG= 623903 
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

Review-Url: https://codereview.chromium.org/2170223002
Cr-Commit-Position: refs/heads/master@{#407290}
Commit  : f2e8191e41dae27a051bc54271fbd971db1bfafd
Date    : Fri Jul 22 22:56:37 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev   N  Good?
chromium@407210  188.341  0.25451   5  good
chromium@407261  185.587  0.488319  5  good
chromium@407285  205.717  0.510973  8  good
chromium@407289  203.093  7.85768   8  good
chromium@407290  185.398  0.73963   8  bad    <--
chromium@407291  185.267  1.73732   8  bad
chromium@407292  186.059  0.296718  8  bad
chromium@407299  185.244  0.745017  5  bad
chromium@407312  167.647  2.67074   5  bad

Bisect job ran on: winx64_zen_perf_bisect
Bug ID: 631038

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests blink_perf.canvas
Test Metric: putImageData/putImageData
Relative Change: 10.99%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/314
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005796618581056880


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

| 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 9 by primiano@chromium.org, Aug 1 2016

Owner: junov@chromium.org
Assigning to test owner. Bisects are finding completely random results sadly. :/

Comment 10 by qyears...@chromium.org, Aug 18 2016 

Perf sheriff ping: reminder to follow up on possible performance issues

Comment 11 by jasontiller@chromium.org, Sep 23 2016 

@junov, any insights about this test? It seems to be pretty noisy.

Comment 12 by junov@chromium.org, Sep 23 2016

Status: WontFix (was: Assigned)
I agree it is a noisy test. This particular alert appears to have recovered in the range 409208 - 409331
Current performance is even higher.
So I think we should close this.
►

Sign in to add a comment