Adjust callers and networking delegates in chrome/ to modified APIs

chrome/browser/android/offline_pages/offline_page_request_job_unittest.cc

Index: chrome/browser/android/offline_pages/offline_page_request_job_unittest.cc
diff --git a/chrome/browser/android/offline_pages/offline_page_request_job_unittest.cc b/chrome/browser/android/offline_pages/offline_page_request_job_unittest.cc
index 35f8e56db2e4e6c326a11b313988088a30819a65..d550661dc30458bc1b9b81304b9b1b98359c68e3 100644
--- a/chrome/browser/android/offline_pages/offline_page_request_job_unittest.cc
+++ b/chrome/browser/android/offline_pages/offline_page_request_job_unittest.cc
@@ -101,8 +101,9 @@ class TestURLRequestDelegate : public net::URLRequest::Delegate {
       : read_completed_callback_(callback),
         buffer_(new net::IOBuffer(kBufSize)) {}
 
-  void OnResponseStarted(net::URLRequest* request) override {
-    if (!request->status().is_success()) {
+  void OnResponseStarted(net::URLRequest* request, int net_error) override {
+    DCHECK_NE(net::ERR_IO_PENDING, net_error);

[dewittj, 2016/09/22 16:27:06]

This DCHECK seems wrong.  I can see two cases here:
* I'm likely to get an IO_PENDING message for normal usage.  In that case we
should just return early.
* I'm not likely to get an IO_PENDING message; then the net::OK check seems
fine.

Neither case should require a DCHECK, right?

[maksims (do not use this acc), 2016/09/29 12:43:14]

Actually, IO_PENDING must not arrive here. It's just a check.

+    if (net_error != net::OK) {
       read_completed_callback_.Run(0);
       return;
     }