Do not monitor system power state during unit tests.

base/test_suite.h

 // Copyright (c) 2006-2008 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.
 
 #ifndef BASE_TEST_SUITE_H_
 #define BASE_TEST_SUITE_H_
 
 // Defines a basic test suite framework for running gtest based tests.  You can
 // instantiate this class in your main function and call its Run method to run
 // any gtest based tests that are linked into your executable.
 
 #include "base/at_exit.h"
 #include "base/base_paths.h"
 #include "base/command_line.h"
 #include "base/debug_on_start.h"
 #include "base/file_path.h"
 #include "base/icu_util.h"
 #include "base/logging.h"
 #include "base/multiprocess_test.h"
 #include "base/scoped_nsautorelease_pool.h"
+#include "base/time.h"
 #include "testing/gtest/include/gtest/gtest.h"
 #include "testing/multiprocess_func_list.h"
 
 #if defined(OS_WIN)
 #include <windows.h>
 #elif defined(OS_LINUX)
 #include <gtk/gtk.h>
 #endif
 
 class TestSuite {
@@ skipping 70 matching lines @@
     FilePath log_filename = exe.ReplaceExtension(FILE_PATH_LITERAL("log"));
     logging::InitLogging(log_filename.value().c_str(),
                          logging::LOG_TO_BOTH_FILE_AND_SYSTEM_DEBUG_LOG,
                          logging::LOCK_LOG_FILE,
                          logging::DELETE_OLD_LOG_FILE);
     // We want process and thread IDs because we may have multiple processes.
     // Note: temporarily enabled timestamps in an effort to catch bug 6361.
     logging::SetLogItems(true, true, true, true);
 
 #if defined(OS_WIN)
+    // We don't want to use SystemMonitor power state monitoring in tests,
+    // so enable high resolution timer unconditionally.
+    base::Time::EnableHiResClockForTests();

[Mike Belshe, 2009/05/26 15:41:20]

I think this comment will lose value over time because we won't remember why "we
don't want to use SystemMonitor ... in tests".

How about:
"For unittests we turn on the high resolution timer and disable base:Time's use
of SystemMonitor.  Unittests start/stop the message loop in ways which don't
work with the SystemMonitor.  See bug
http://code.google.com/p/chromium/issues/detail?id=12187"

+
     // In some cases, we do not want to see standard error dialogs.
     if (!IsDebuggerPresent() &&
         !CommandLine::ForCurrentProcess()->HasSwitch(L"show-error-dialogs")) {
       SuppressErrorDialogs();
 #if !defined(PURIFY)
       // When the code in this file moved around, bug 6436 resurfaced.
       // As a hack workaround, just #ifdef out this code for Purify builds.
       logging::SetLogAssertHandler(UnitTestAssertHandler);
-#endif
+#endif  // !defined(PURIFY)
     }
-#endif
+#endif  // defined(OS_WIN)
 
     icu_util::Initialize();
   }
 
   virtual void Shutdown() {
   }
 
   // Make sure that we setup an AtExitManager so Singleton objects will be
   // destroyed.
   base::AtExitManager at_exit_manager_;
 };
 
 #endif  // BASE_TEST_SUITE_H_