Believe this causes the valgrind linux test failures. Since it is a small change I decided to revert

instead of disable the test.

Revert 32807 - The async notification via OnReadComplete was still posting
a callback through this message loop.  This makes it difficult
to write tests, as callbacks already scheduled will go in
front of the OnReadComplete().  Treat the notifications through
OnReadComplete as synchronous always.

This doesn't effect existing tests, but makes my new tests
possible.

TBR=mbelshe
BUG=none
TEST=this is the test!

Review URL: http://codereview.chromium.org/414073

TBR=mbelshe@google.com
Review URL: http://codereview.chromium.org/431016

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

1 files changed, 3 insertions, 7 deletions

diff --git a/net/socket/socket_test_util.cc b/net/socket/socket_test_util.cc
index 18ece28..ef10f76 100644
--- a/net/socket/socket_test_util.cc
+++ b/net/socket/socket_test_util.cc
@@ -150,17 +150,13 @@ void MockTCPClientSocket::OnReadComplete(const MockRead& data) {
   DCHECK_NE(ERR_IO_PENDING, data.result);
   // Since we've been waiting for data, need_read_data_ should be true.
   DCHECK(need_read_data_);
+  // In order to fire the callback, this IO needs to be marked as async.
+  DCHECK(data.async);
 
   read_data_ = data;
   need_read_data_ = false;
 
-  // The caller is simulating that this IO completes right now.  Don't
-  // let CompleteRead() schedule a callback.
-  read_data_.async = false;
-
-  net::CompletionCallback* callback = pending_callback_;
-  int rv = CompleteRead();
-  RunCallback(callback, rv);
+  CompleteRead();
 }
 
 int MockTCPClientSocket::CompleteRead() {