Name the main unit_tests thread

When profiling unit_tests for various performance issues it is hard to
find the main thread if it isn't named - so name it.

Change-Id: I01eb3014bb896c095358abd7f778df4b043c3581
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1577788
Reviewed-by: Marc Treib <treib@chromium.org>
Commit-Queue: Bruce Dawson <brucedawson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#653267}
diff --git a/chrome/test/base/run_all_unittests.cc b/chrome/test/base/run_all_unittests.cc
index a69c7eb..ea8716e8 100644
--- a/chrome/test/base/run_all_unittests.cc
+++ b/chrome/test/base/run_all_unittests.cc
@@ -6,6 +6,7 @@
 #include "base/command_line.h"
 #include "base/test/launcher/unit_test_launcher.h"
 #include "base/test/test_io_thread.h"
+#include "base/threading/platform_thread.h"
 #include "build/build_config.h"
 #include "chrome/test/base/chrome_unit_test_suite.h"
 #include "content/public/test/unittest_test_suite.h"
@@ -16,6 +17,8 @@
 #endif
 
 int main(int argc, char **argv) {
+  base::PlatformThread::SetName("MainThread");
+
   content::UnitTestTestSuite test_suite(new ChromeUnitTestSuite(argc, argv));
 
   base::TestIOThread test_io_thread(base::TestIOThread::kAutoStart);