From 0753fed7b6ecb24af3640426573434bf43902478 Mon Sep 17 00:00:00 2001 From: "evan@chromium.org" Date: Thu, 8 Jul 2010 18:25:10 +0000 Subject: Mark two tests flaky. They triy to use a timeout to reduce flakiness, but that only makes them fail less often; they are still not completely reliable. BUG=48562 Review URL: http://codereview.chromium.org/2901003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@51867 0039d316-1c4b-4281-b951-d872f2087c98 --- chrome/browser/debugger/devtools_remote_listen_socket_unittest.cc | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'chrome/browser/debugger') diff --git a/chrome/browser/debugger/devtools_remote_listen_socket_unittest.cc b/chrome/browser/debugger/devtools_remote_listen_socket_unittest.cc index 79933fe..2fa5212 100644 --- a/chrome/browser/debugger/devtools_remote_listen_socket_unittest.cc +++ b/chrome/browser/debugger/devtools_remote_listen_socket_unittest.cc @@ -343,7 +343,9 @@ class DevToolsRemoteListenSocketTest: public PlatformTest { scoped_refptr tester_; }; -TEST_F(DevToolsRemoteListenSocketTest, ServerSend) { +// This test is flaky; see comment in ::TestServerSend. +// http://code.google.com/p/chromium/issues/detail?id=48562 +TEST_F(DevToolsRemoteListenSocketTest, FLAKY_ServerSend) { tester_->TestServerSend(); } -- cgit v1.1