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

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


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

chromium-rel-mac11

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

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

Hi dpranke@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 : Revert of Flip remaining main Mac bots to GN. (patchset #1 id:1 of https://codereview.chromium.org/2136293002/ )
Author  : dpranke
Commit description:
  
Reason for revert:
"Mac" builder on /p/chromium fails follow-up ninja build claiming that things are dirty:

https://build.chromium.org/p/chromium/builders/Mac/builds/17564/steps/compile/logs/stdio

The official.desktop.continuous builder is breaking due to the missing remoting crashreporting link that I had thought I fixed but maybe forgot to land ...

Original issue's description:
> Flip remaining main Mac bots to GN.
>
> This flips the remaining main Mac bots to GN, e.g.:
>
> - chromium
>   - Mac
> - chromium.chrome
>   - Google Mac
> - chromium.perf
>   - Mac Builder
> - official.desktop
>   - mac64
> - official.desktop.continuous
>   - mac trunk
>
> There are various FYI and memory builders still, plus the GYP
> builder on the chromium.mac waterfall.
>
> R=rsesek@chromium.org
> NOTRY=true
> BUG= 618468 
>
> Committed: https://crrev.com/f7d150aa0ad0c54760d5593ac04afee50e1e5286
> Cr-Commit-Position: refs/heads/master@{#404744}

TBR=rsesek@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG= 618468 

Review-Url: https://codereview.chromium.org/2138313002
Cr-Commit-Position: refs/heads/master@{#404765}
Commit  : f746c62413f7db8758bb21750af0d98938f3308a
Date    : Tue Jul 12 01:53:00 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@404764  4420.46  13.9071  5  good
chromium@404765  4130.67  22.2792  5  bad    <--
chromium@404766  4112.53  30.331   5  bad
chromium@404767  4132.36  16.424   5  bad
chromium@404769  4120.32  20.0852  5  bad
chromium@404773  4095.17  40.5846  5  bad

Bisect job ran on: mac_10_11_perf_bisect
Bug ID: 627505

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests blink_perf.css
Test Metric: PseudoClassSelectors/PseudoClassSelectors
Relative Change: 7.36%
Score: 99.9

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


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

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

It's possible something is slower w/ GYP than w/ GN. We'll be landing this CL again soon, so I'm going to ignore this for now.