Views views_unittests native widget tests leak

tools/valgrind/chrome_tests.py

Index: tools/valgrind/chrome_tests.py
diff --git a/tools/valgrind/chrome_tests.py b/tools/valgrind/chrome_tests.py
index c569b0079729c65f47be291cce465733abf39b14..6f86751adc17dff4c0846480d6d9e67385c21fa6 100755
--- a/tools/valgrind/chrome_tests.py
+++ b/tools/valgrind/chrome_tests.py
@@ -272,6 +272,9 @@ class ChromeTests:
   def TestGfx(self):
     return self.SimpleTest("chrome", "gfx_unittests")
 
+  def TestViews(self):
+    return self.SimpleTest("views", "views_unittests")

[Timur Iskhodzhanov, 2011/06/29 09:24:01]

a few questions:
a) is it single-process?
b) how long does it run under Valgrind?
c) should we add it to the memory waterfall?

+
   # Valgrind timeouts are in seconds.
   UI_VALGRIND_ARGS = ["--timeout=7200", "--trace_children", "--indirect"]
   # UI test timeouts are in milliseconds.
@@ -445,6 +448,7 @@ class ChromeTests:
     "app": TestApp,              "app_unittests": TestApp,
     "ui_unit": TestUIUnit,       "ui_unittests": TestUIUnit,
     "gfx": TestGfx,              "gfx_unittests": TestGfx,
+    "views": TestViews,          "views_unittests": TestViews,
   }
 
 def _main(_):