Stop building ui_unittests target.

ui/chromeos/touch_exploration_controller_unittest.cc

Index: ui/chromeos/touch_exploration_controller_unittest.cc
diff --git a/ui/chromeos/touch_exploration_controller_unittest.cc b/ui/chromeos/touch_exploration_controller_unittest.cc
index 201aefd54146a04f2ec51ff898635166c51e3909..72d20756d498fc9b93508e59c3483ddc4a70a4dc 100644
--- a/ui/chromeos/touch_exploration_controller_unittest.cc
+++ b/ui/chromeos/touch_exploration_controller_unittest.cc
@@ -469,8 +469,8 @@ void ConfirmEventsAreKeyAndEqual(ui::Event* e1, ui::Event* e2) {
   ASSERT_NO_FATAL_FAILURE(ConfirmEventsAreKeyAndEqual(e1, e2))
 
 // TODO(mfomitchev): Need to investigate why we don't get mouse enter/exit
-// events when running these tests as part of ui_unittests. We do get them when
-// the tests are run as part of ash unit tests.
+// events when running these tests as part of ui_base_unittests. We do get them
+// when the tests are run as part of ash unit tests.
 
 // If a swipe has been successfully completed, then six key events will be
 // dispatched that correspond to shift+search+direction