Wildcard the test cases if two or more tests make

ThreadSanitizer hang.
Usually, if several tests hang in the same way, that means there's some common code between them that makes TSAN's address space manager unhappy.
Then it's likely that a new test from the same test case exploits the same code and breaks ThreadSanitizer again.
BUG=http://code.google.com/p/data-race-test/issues/detail?id=11
TBR=dank
Review URL: http://codereview.chromium.org/335024

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@30043 0039d316-1c4b-4281-b951-d872f2087c98

net/data/valgrind/net_unittests.gtest-tsan_mac.txt

@@ -18,10 +18,8 @@ URLRequestTestHTTP.*
 URLRequestTestFTP.*
 SSLClientSocketTest.*
 DiskCacheTest.*
-DiskCacheEntryTest.*Async*
-DiskCacheEntryTest.CancelSparseIO
-DiskCacheEntryTest.DoomSparseEntry
-FlipNetworkTransactionTest.Connect
+DiskCacheEntryTest.*
+FlipNetworkTransactionTest.*
 
 # WebSocketTest tests are extraordinary slow under ThreadSanitizer,
 # (see http://crbug.com/25392)

net/data/valgrind/net_unittests.gtest.txt

@@ -14,4 +14,3 @@ DiskCacheBackendTest.NewEvictionInvalidEntryWithLoad
 DiskCacheBackendTest.NewEvictionTrimInvalidEntry
 DiskCacheBackendTest.NewEvictionTrimInvalidEntry2
 DiskCacheBackendTest.NewEvictionInvalidEntryEnumeration
-FlipNetworkTransactionTest.ResponseWithoutSynReply