Revert of telemetry: Fix startup benchmarks so that all metrics get recorded.

Revert of telemetry: Fix startup benchmarks so that all metrics get recorded.

Reason for revert:
Theoretically, these changes should no longer be required, now that
https://code.google.com/p/chromium/issues/detail?id=529340#c7 has landed.

Original issue's description:
> telemetry: Fix startup benchmarks so that all metrics get recorded.
>
> *PERF SHERRIF: if startup benchmarks become red, this CL is to be reverted.
>
> The lack of a page navigation was preventing the metric
> Startup.FirstWebContents.NonEmptyPaint from being emitted. The addition of the
> RAF logic check is to prevent theoretical race conditions - it may be overkill.
>
> BUG=513364
> CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:linux_perf_bisect;tryserver.chromium.perf:mac_perf_bisect;tryserver.chromium.perf:android_nexus5_perf_bisect
>
> Committed: https://crrev.com/0bc400e1c96da5a05379bc1b634ec278f36d3417
> Cr-Commit-Position: refs/heads/master@{#347402}

TBR=nednguyen@google.com
BUG=513364
CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:linux_perf_bisect;tryserver.chromium.perf:mac_10_10_perf_bisect;tryserver.chromium.perf:win_perf_bisect;tryserver.chromium.perf:android_nexus5_perf_bisect

Committed: https://crrev.com/359e8b1514eba38cb34d72443c223f49d1a55656
Cr-Commit-Position: refs/heads/master@{#359024}

[erikchen, 2015-11-10 22:15:53]

Created Revert of telemetry: Fix startup benchmarks so that all metrics get
recorded.

[commit-bot: I haz the power, 2015-11-10 22:17:27]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1438533003/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1438533003/1

[commit-bot: I haz the power, 2015-11-10 22:19:03]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-11-10 22:19:03]

Failed to apply patch for tools/perf/page_sets/blank_page.py:
While running git apply --index -3 -p1;
  error: patch failed: tools/perf/page_sets/blank_page.py:9
  Falling back to three-way merge...
  Applied patch to 'tools/perf/page_sets/blank_page.py' with conflicts.
  U tools/perf/page_sets/blank_page.py

Patch:       tools/perf/page_sets/blank_page.py
Index: tools/perf/page_sets/blank_page.py
diff --git a/tools/perf/page_sets/blank_page.py
b/tools/perf/page_sets/blank_page.py
index
92d46b01f539c1833d3121eb3874097eaa2943b3..6f87074b3f80a86df5893196d7212671e7400a6c
100644
--- a/tools/perf/page_sets/blank_page.py
+++ b/tools/perf/page_sets/blank_page.py
@@ -9,18 +9,6 @@
   def __init__(self, url, page_set):
     super(BlankPage, self).__init__(url, page_set=page_set)
 
-  def RunPageInteractions(self, action_runner):
-    # Request a RAF and wait for it to be processed to ensure that the metric
-    # Startup.FirstWebContents.NonEmptyPaint is recorded.
-    action_runner.ExecuteJavaScript(
-        """
-        this.hasRunRAF = 0;
-        requestAnimationFrame(function() {
-            this.hasRunRAF = 1;
-        });
-        """
-    )
-    action_runner.WaitForJavaScriptCondition("this.hasRunRAF == 1")
 
 class BlankPageSet(story.StorySet):
   """A single blank page."""

[commit-bot: I haz the power, 2015-11-10 22:20:15]

The CQ bit was unchecked by commit-bot@chromium.org

[erikchen, 2015-11-10 22:23:25]

The CQ bit was checked by erikchen@chromium.org

[commit-bot: I haz the power, 2015-11-10 22:25:06]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1438533003/70001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1438533003/70001

[commit-bot: I haz the power, 2015-11-11 00:19:48]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-11-11 00:19:49]

Try jobs failed on following builders:
  win_chromium_rel_ng on tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)

[erikchen, 2015-11-11 00:20:53]

On 2015/11/11 00:19:49, commit-bot: I haz the power wrote:
> Try jobs failed on following builders:
>   win_chromium_rel_ng on tryserver.chromium.win (JOB_FAILED,
>
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)

  CredentialsError: Attempted to access a file from Cloud Storage but you have
no configured credentials. To configure your credentials:
    1. Run
"e:\b\swarm_slave\work\isolated\runzed0k7\tools\telemetry\third_party\gsutilz\gsutil
config" and follow its instructions.
    2. If you have a @google.com account, use that account.
    3. For the project-id, just enter 0.

[erikchen, 2015-11-11 00:20:58]

The CQ bit was checked by erikchen@chromium.org

[commit-bot: I haz the power, 2015-11-11 00:22:40]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1438533003/70001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1438533003/70001

[nednguyen, 2015-11-11 00:33:25]

On 2015/11/11 00:20:53, erikchen wrote:
> On 2015/11/11 00:19:49, commit-bot: I haz the power wrote:
> > Try jobs failed on following builders:
> >   win_chromium_rel_ng on tryserver.chromium.win (JOB_FAILED,
> >
>
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)
> 
>   CredentialsError: Attempted to access a file from Cloud Storage but you have
> no configured credentials. To configure your credentials:
>     1. Run
>
"e:\b\swarm_slave\work\isolated\runzed0k7\tools\telemetry\third_party\gsutilz\gsutil
> config" and follow its instructions.
>     2. If you have a @google.com account, use that account.
>     3. For the project-id, just enter 0.

That's crbug.com/553994

[commit-bot: I haz the power, 2015-11-11 02:34:14]

Committed patchset #2 (id:70001)

[commit-bot: I haz the power, 2015-11-11 02:34:57]

Patchset 2 (id:??) landed as
https://crrev.com/359e8b1514eba38cb34d72443c223f49d1a55656
Cr-Commit-Position: refs/heads/master@{#359024}

[erikchen, 2015-11-24 18:51:04]

A revert of this CL (patchset #2 id:70001) has been created in
https://codereview.chromium.org/1475773003/ by erikchen@chromium.org.

The reason for reverting is: Looks like my changes were still required to get
the metric:

foreground_tab_request_start

https://code.google.com/p/chromium/issues/detail?id=560760&q=owner%3Aerikchen....