Add sync_integration_tests support to valgrind's chrome_tests.sh.

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 bd59339fbd55b93caaab25391b7f1966bad76ec9..3beb585b3ee3f5528c4ff37f8151087220a566f0 100755
--- a/tools/valgrind/chrome_tests.py
+++ b/tools/valgrind/chrome_tests.py
@@ -307,6 +307,9 @@ class ChromeTests:
   def TestSync(self):
     return self.SimpleTest("chrome", "sync_unit_tests")
 
+  def TestSyncIntegration(self):
+    return self.SimpleTest("chrome", "sync_integration_tests")

[Timur Iskhodzhanov, 2011/02/17 10:37:02]

What are sync_integration_tests?

Do they spawn Chrome processes?

[Timur Iskhodzhanov, 2011/02/17 10:39:13]

Self-answer: yes, they do.

In this case, you should better copy the TestSafeBrowsing or TestInteractiveUI
instead of TestSync.

On 2011/02/17 10:37:02, Timur Iskhodzhanov wrote:

[Nicolas Zea, 2011/02/17 21:07:51]

Done.

+
   def TestLayoutChunk(self, chunk_num, chunk_size):
     # Run tests [chunk_num*chunk_size .. (chunk_num+1)*chunk_size) from the
     # list of tests.  Wrap around to beginning of list at end.
@@ -428,6 +431,7 @@ class ChromeTests:
     "safe_browsing": TestSafeBrowsing, "safe_browsing_tests": TestSafeBrowsing,
     "startup": TestStartup,      "startup_tests": TestStartup,
     "sync": TestSync,            "sync_unit_tests": TestSync,
+    "sync_integration_tests": TestSyncIntegration,

[Timur Iskhodzhanov, 2011/02/17 10:37:02]

You may also add
"sync_integration": TestSyncIntegration,

That'd be useful when setting up a valgrind bot because otherwise you'll need to
name a test run target as
vagrlind_sync_integration_tests
:)

[Nicolas Zea, 2011/02/17 21:07:51]

Done.

     "test_shell": TestTestShell, "test_shell_tests": TestTestShell,
     "ui": TestUI,                "ui_tests": TestUI,
     "unit": TestUnit,            "unit_tests": TestUnit,