Bisect job here: https://chromeperf.appspot.com/buildbucket_job_status/9015662758753752528

This time again, with the *right* revision range: https://chromeperf.appspot.com/buildbucket_job_status/9015658757004859504

And _this_ time, with the right revision _and_ the right bisect type (return code): https://chromeperf.appspot.com/buildbucket_job_status/9015655100136325744

Reduced repeat count to 5 at eakuefner's suggestion: https://chromeperf.appspot.com/buildbucket_job_status/9015652120733135440

(Also, the actual revision range is 384314 to 384620)

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

Hi wnwen@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 : Propagate is_official_build to version script.
Author  : wnwen
Commit description:
  
OFFICIAL_BUILD is a special variable in the version script which
takes its value from the environment variable. This means that local
builds with is_official_build will not actually result in
ChromeVersionConstants.isOfficialBuild() returning true.

This CL propagates the is_official_build truthiness to the script so
official builds no longer depend solely on the environment variable.

BUG= 599268 

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

Cr-Commit-Position: refs/heads/master@{#384340}
Commit  : eab85df0275b825e428954c4030e358ce968ecd9
Date    : Thu Mar 31 18:36:33 2016


===== TESTED REVISIONS =====
Revision                Exit Code   Std. Dev.   Num Values  Good?
chromium@384314         0           N/A         5           good
chromium@384334         0           N/A         5           good
chromium@384339         0           N/A         5           good
chromium@384340         1           N/A         5           bad         <-
chromium@384341         1           N/A         5           bad
chromium@384342         1           N/A         5           bad
chromium@384344         1           N/A         5           bad
chromium@384353         1           N/A         5           bad
chromium@384391         1           N/A         5           bad
chromium@384467         1           N/A         5           bad
chromium@384620         1           N/A         5           bad

Bisect job ran on: android_s5_perf_bisect
Bug ID: 602297

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --also-run-disabled-tests blink_style.key_mobile_sites
Test Metric: parse_css_enormous_tokens/http___www.boingboing.net
Relative Change: Zero to non-zero
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/593
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9015652120733135440


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

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

This CL was reverted and relanded after fixing the root cause. 

Closing this as a duplicate of 600377