Switch to standard integer types in components/, part 2 of 4.

components/history/content/browser/content_history_backend_db_unittest.cc

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 // History unit tests come in two flavors:
 //
 // 1. The more complicated style is that the unit test creates a full history
 //    service. This spawns a background thread for the history backend, and
 //    all communication is asynchronous. This is useful for testing more
 //    complicated things or end-to-end behavior.
 //
 // 2. The simpler style is to create a history backend on this thread and
 //    access it directly without a HistoryService object. This is much simpler
 //    because communication is synchronous. Generally, sets should go through
 //    the history backend (since there is a lot of logic) but gets can come
 //    directly from the HistoryDatabase. This is because the backend generally
 //    has no logic in the getter except threading stuff, which we don't want
 //    to run.
 
 #include "components/history/core/browser/history_backend.h"
 
+#include <stddef.h>
+
+#include "base/macros.h"
 #include "components/history/core/test/history_backend_db_base_test.h"
 
 namespace history {
 namespace {
 
 // This must be outside the anonymous namespace for the friend statement in
 // HistoryBackend to work.
 class ContentHistoryBackendDBTest : public HistoryBackendDBBaseTest {
  public:
   ContentHistoryBackendDBTest() {}
@@ skipping 87 matching lines @@
     }
 
     EXPECT_TRUE(found)
         << "Error \"" << cur_reason.name << "\" not found in historical list."
         << std::endl
         << "Please add it.";
   }
 }
 }  // namespace
 }  // namespace history