ui/base: Remove ui_unittests target.

ui/base/ui_base_tests_bundle.gypi

Index: ui/base/ui_base_tests_bundle.gypi
diff --git a/ui/base/ui_base_tests_bundle.gypi b/ui/base/ui_base_tests_bundle.gypi
index 8fb6307339560bfff7be281243cf8c7622245812..2eeabe88a68f15af2e9b303ac363da4d95b3f8e7 100644
--- a/ui/base/ui_base_tests_bundle.gypi
+++ b/ui/base/ui_base_tests_bundle.gypi
@@ -2,7 +2,7 @@
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
-# This file contains resources for the ui_unittests test bundle.
+# This file contains resources for the ui_base_unittests test bundle.
 # See chrome_dll_bundle.gypi for a description of the techniques here.
 {
   'product_name': 'ui_unittests Framework',

[tfarina, 2014/11/23 16:52:39]

Nico, Trent, is it fine to change this name in this CL? I was planning to rename
it in a follow up, as I don't know if it is fine or not. Not sure how it will
effect iOS/Mac build.

[tapted, 2014/11/23 22:12:32]

So long as the string literal in ui/base/test/run_all_unittests.cc is updated at
the same time, nothing comes to mind that might explode.

I'd also consider not renaming it. It doesn't have a dependency on
ui_base_unittests, and lots of test targets that are not "ui_base" use
ui_test.pak. This Framework bundle is just a wrapper around ui_test.pak. If,
say, app_list_unittests wanted a (semi)proper app bundle, it could re-use this.

So, not renaming is probably my preference, but I don't have strong feelings
about it.

[tfarina, 2014/11/24 17:23:44]

Thanks Trent. I will let that for a follow up CL then.