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

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


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

android-one

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

=== Auto-CCing suspected CL author jbriance@cisco.com ===

Hi jbriance@cisco.com, the bisect results pointed to your CL, please take a look at the
results.


=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : jbriance
  Commit : 5bd06e2b5019b1ab0337083a926a8f672255e065
  Date   : Wed Jan 04 09:02:11 2017
  Subject: Add gcc_target_rpath gn arg

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:proportional_resident_size_avg/browse_news/browse_news_hackernews
  Change       : 3.19% | 87570654.6667 -> 90364126.6667

Revision             Result                   N
chromium@441343      87570655 +- 6270245      6      good
chromium@441344      91379423 +- 1837994      6      bad       <--
chromium@441345      91235380 +- 1801922      6      bad
chromium@441347      91359113 +- 2084013      6      bad
chromium@441350      91244255 +- 2391915      6      bad
chromium@441356      91255689 +- 723889       6      bad
chromium@441369      90999860 +- 1705657      6      bad
chromium@441394      90364127 +- 1629635      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.hackernews system_health.memory_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8990898303646131680

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5833468069543936


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

> Hi jbriance@cisco.com, the bisect results pointed to your CL, please take a look at the
results.

My change is very unlikely to cause any performance regression. It is supposed to be a no-op, unless you use the new gn arg introduced by the change.

Looks like ref build also changed - so this was likely infrastructure changes.