summaryrefslogtreecommitdiffstats
path: root/base/time_unittest.cc
diff options
context:
space:
mode:
authormbelshe@chromium.org <mbelshe@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-10-20 08:52:32 +0000
committermbelshe@chromium.org <mbelshe@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-10-20 08:52:32 +0000
commit47245d6709f7f16a65cfb3df9aeb51fb32d5a4ea (patch)
tree36051d10c826994d095b116955f42dae2de16e52 /base/time_unittest.cc
parentc4fcdca3cfec4ca060d29d10cdc06dc83aed1bf2 (diff)
downloadchromium_src-47245d6709f7f16a65cfb3df9aeb51fb32d5a4ea.zip
chromium_src-47245d6709f7f16a65cfb3df9aeb51fb32d5a4ea.tar.gz
chromium_src-47245d6709f7f16a65cfb3df9aeb51fb32d5a4ea.tar.bz2
2nd try:
Fix regression where high resolution timers could be activated even under battery power. Add unit test to protect chromium from developers like me in the future. The fix is a one-liner in hi_res_timer_manager_win.cc. The rest of the code change is the mechanics to enable the unit test. BUG=59528 TEST=HiResTimerManagerTest.ToggleOnOff Review URL: http://codereview.chromium.org/3889004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@63191 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'base/time_unittest.cc')
0 files changed, 0 insertions, 0 deletions