Include tab IDs when reporting data use accounting.

chrome/browser/net/chrome_network_delegate_unittest.cc

Index: chrome/browser/net/chrome_network_delegate_unittest.cc
diff --git a/chrome/browser/net/chrome_network_delegate_unittest.cc b/chrome/browser/net/chrome_network_delegate_unittest.cc
index 5fb4b598b806ee26fa372712e6b048871ff46c2e..9c0ef79a4d5341c0605f8109f9a70b578718e2a6 100644
--- a/chrome/browser/net/chrome_network_delegate_unittest.cc
+++ b/chrome/browser/net/chrome_network_delegate_unittest.cc
@@ -105,10 +105,12 @@ class FakeDataUseAggregator : public data_usage::DataUseAggregator {
         off_the_record_rx_bytes_(0) {}
   ~FakeDataUseAggregator() override {}
 
-  void ReportDataUse(const net::URLRequest& request,
-                     int32_t tab_id,
-                     int64_t tx_bytes,
-                     int64_t rx_bytes) override {
+  void ReportDataUse(int64_t tx_bytes,

[tbansal1, 2015/10/26 22:24:29]

Why not keep the request object? Makes it easier if we need to pull something
else out of request.

[sclittle, 2015/10/26 23:56:01]

You're right, but the request might no longer exist after the hop to the UI
thread, so we have to pull everything we need out of it before that hop.

+                     int64_t rx_bytes,
+                     const GURL& url,
+                     const base::Time& request_time,
+                     const GURL& first_party_for_cookies,
+                     int32_t tab_id) override {
     on_the_record_tx_bytes_ += tx_bytes;
     on_the_record_rx_bytes_ += rx_bytes;
   }