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

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


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

chromium-rel-mac11

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9006756182741640896

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

Hi zmo@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 : Vaidate Clear and ClearBuffer calls match the buffer types.
Author  : zmo
Commit description:
  
BUG= 429053 
TEST=webgl2_conformance
R=piman@chromium.org
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/2152213002
Cr-Commit-Position: refs/heads/master@{#405928}
Commit  : 20c5b3b3c34113b83f365def5863b3c41b4b4283
Date    : Sat Jul 16 03:44:43 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@405925  713.213  7.0913   5  good
chromium@405927  705.631  17.8862  5  good
chromium@405928  619.253  13.9204  5  bad    <--
chromium@405930  628.457  4.93773  5  bad
chromium@405934  631.076  4.26851  5  bad

Bisect job ran on: mac_10_11_perf_bisect
Bug ID: 629328

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests blink_perf.parser
Test Metric: query-selector-all-first/query-selector-all-first
Relative Change: 11.52%
Score: 99.9

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


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

| 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!

I'm really surprised this test would be affected by this change...

I am at a conference and won't be able to look into this.

I agree with piman that my CL is very unlikely the cause.

If this perf is still an issue, get someone who owns this parser test to take a look.

Appears recovered now.