Adding a Endure regression test to catch gmail memory issues (crbug.com/345702).

tools/perf/benchmarks/endure.py

Index: tools/perf/benchmarks/endure.py
===================================================================
--- tools/perf/benchmarks/endure.py	(revision 253614)
+++ tools/perf/benchmarks/endure.py	(working copy)
@@ -16,6 +16,15 @@
       'perf_stats_interval': '100s'
   }
 
+class _EndureGmailRefresh(test.Test):
+  test = endure.Endure
+  # Default options for endure benchmarks. Could be overridden in subclasses.
+  options = {
+      'skip_navigate_on_repeat': True,
+      'page_repeat_secs': 300,
+      'perf_stats_interval': '1'

[qyearsley, 2014/03/05 00:44:27]

Here, the number of times to repeat the page is specified in seconds and the
interval between measuring is specified in number of repetitions. I think that
this is fine, but it's worth noting that you could change to repeating for a
certain number of times by using the property "page_repeat_iters" instead.

(This option is used the module
src/tools/telemetry/telemetry/page/page_runner_repeat.py added last year by
Edmund...)

+  }
+
 class EndureCalendarForwardBackward(_EndureBenchmark):
   page_set = 'page_sets/calendar_forward_backward.json'
 
@@ -47,3 +56,6 @@
 class EndurePlusAltPostsPhotos(_EndureBenchmark):
   page_set = 'page_sets/plus_alt_posts_photos.json'
 
+class EndureGmailRefresh( _EndureGmailRefresh):
+  page_set = 'page_sets/endure_gmail_refresh.json'

[qyearsley, 2014/03/05 00:44:27]

Since this is the only subclass of _EndureGmailRefresh, it would also be
possible to just define test and options here and make this a direct subclass of
test.Test.

(But it's no big deal in this file since it's not too complicated.)

+