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

Issue 596485 link

Starred by 0 users

Issue metadata

Status: Duplicate
Merged: issue 596475
Owner:
Last visit > 30 days ago
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3.5% regression in smoothness.gpu_rasterization.top_25_smooth at 382064:382133

Project Member Reported by alexclarke@chromium.org, Mar 21 2016

Issue description

This might be a duplicate, there as  a nexus5x regression here too.  Lets see what the bot finds.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=596485

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


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

chromium-rel-mac11
Kicked off a bisect on Twitter since it seems to have regressed the most: https://chromeperf.appspot.com/buildbucket_job_status/9016893714294519360
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Mar 29 2016


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


===== SUSPECTED CL(s) =====
Subject : Add CONTEXT_TYPE_OPENGLES2_PEPPER
Author  : ericrk
Commit description:
  
Adds a new context type for Pepper GL contexts. This allows us to
fine tune driver bug workarounds for pepper vs. non-pepper contexts.

Currently used to disable the Intel MSAA blacklist on pepper contexts,
as it should be up to the app whether to use MSAA.

BUG= 527565 
CQ_INCLUDE_TRYBOTS=tryserver.chromium.win:win_optional_gpu_tests_rel;tryserver.chromium.mac:mac_optional_gpu_tests_rel

Review URL: https://codereview.chromium.org/1781093002

Cr-Commit-Position: refs/heads/master@{#382097}
Commit  : d72af43d432d9def9ce591b7167c19b7b1581e30
Date    : Fri Mar 18 21:45:56 2016


===== TESTED REVISIONS =====
Revision                Mean Value  Std. Dev.   Num Values  Good?
chromium@382063         31.2278     1.420032    5           good
chromium@382084         31.9508     1.26121     5           good
chromium@382092         31.7338     0.791276    5           good
chromium@382096         31.2578     0.926243    5           good
chromium@382097         75.9422     2.417755    5           bad         <-
chromium@382098         71.7022     4.366614    5           bad
chromium@382099         72.47       1.678752    5           bad
chromium@382133         72.988      1.356074    5           bad

Bisect job ran on: mac_10_11_perf_bisect
Bug ID: 596485

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --also-run-disabled-tests smoothness.gpu_rasterization.top_25_smooth
Test Metric: mean_input_event_latency/Twitter
Relative Change: 133.73%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_11_perf_bisect/builds/556
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9016893714294519360


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

| 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