Updates to base unittests so they run correctly in libchrome on Android

base/command_line_unittest.cc

Index: base/command_line_unittest.cc
diff --git a/base/command_line_unittest.cc b/base/command_line_unittest.cc
index 018d83f1add248ca85f8825a6789cb477fb7b1b1..ac8a39567c31d3e39fad2c5a7e5ef6533d02c401 100644
--- a/base/command_line_unittest.cc
+++ b/base/command_line_unittest.cc
@@ -378,6 +378,9 @@ TEST(CommandLineTest, ProgramQuotes) {
 
 // Calling Init multiple times should not modify the previous CommandLine.
 TEST(CommandLineTest, Init) {
+  // Call Init without checking output once so we know it's been called
+  // whether or not the test runner does so.

[Daniel Erat, 2015/08/10 21:51:17]

just for brett's benefit since we discussed this on the other bug: the chromium
test runner calls CommandLine::Init(), which seems fairly gross since this test
later exercises the singleton. on the brillo side, the default gtest harness is
being used, so Init() doesn't get called automatically.

calling Init() explicitly here seems reasonable to me: the test is still
checking that a later call to Init() returns false and doesn't recreate the
singleton, but it also makes the test stop depending on outside code calling
Init() first.

+  CommandLine::Init(0, NULL);
   CommandLine* initial = CommandLine::ForCurrentProcess();
   EXPECT_FALSE(CommandLine::Init(0, NULL));
   CommandLine* current = CommandLine::ForCurrentProcess();