[tools/perf] Explicitly disable state tear down on some benchmarks

tools/perf/benchmarks/memory_infra.py

Index: tools/perf/benchmarks/memory_infra.py
diff --git a/tools/perf/benchmarks/memory_infra.py b/tools/perf/benchmarks/memory_infra.py
index ce8f3516e0280851509f93c9741c528a6f157c8d..1e03843c3aa8e3e270c87883f8ece7c231a1395b 100644
--- a/tools/perf/benchmarks/memory_infra.py
+++ b/tools/perf/benchmarks/memory_infra.py
@@ -62,6 +62,10 @@ class MemoryBenchmarkTop10Mobile(_MemoryInfra):
     return 'memory.top_10_mobile'
 
   @classmethod
+  def ShouldTearDownStateAfterEachStoryRun(cls):
+    return False
+
+  @classmethod
   def ShouldDisable(cls, possible_browser):
     # TODO(crbug.com/586148): Benchmark should not depend on DeskClock app.
     return not possible_browser.platform.CanLaunchApplication(
@@ -108,6 +112,10 @@ class DualBrowserBenchmark(_MemoryInfra):
     return 'memory.dual_browser_test'
 
   @classmethod
+  def ShouldTearDownStateAfterEachStoryRun(cls):
+    return False
+
+  @classmethod
   def ValueCanBeAddedPredicate(cls, value, is_first_result):
     # TODO(crbug.com/610962): Remove this stopgap when the perf dashboard
     # is able to cope with the data load generated by TBMv2 metrics.
@@ -130,6 +138,10 @@ class LongRunningDualBrowserBenchmark(_MemoryInfra):
     return 'memory.long_running_dual_browser_test'
 
   @classmethod
+  def ShouldTearDownStateAfterEachStoryRun(cls):
+    return False
+
+  @classmethod
   def ShouldTearDownStateAfterEachStorySetRun(cls):
     return False