Android gtest runner: Use first test list result rather than merging

build/android/pylib/local/device/local_device_gtest_run.py

Index: build/android/pylib/local/device/local_device_gtest_run.py
diff --git a/build/android/pylib/local/device/local_device_gtest_run.py b/build/android/pylib/local/device/local_device_gtest_run.py
index 0f360d4a9e943045c946f68689f98788fd2966e9..9369959ed2af3e17900d073976d8106356a15d50 100644
--- a/build/android/pylib/local/device/local_device_gtest_run.py
+++ b/build/android/pylib/local/device/local_device_gtest_run.py
@@ -229,9 +229,8 @@ class LocalDeviceGtestRun(local_device_test_run.LocalDeviceTestRun):
       tests = self._test_instance.FilterTests(tests)
       return tests
 
-    test_lists = self._env.parallel_devices.pMap(list_tests).pGet(None)
-    tests = list(sorted(set().union(*[set(tl) for tl in test_lists if tl])))
-    return tests
+    # Result should be the same for all devices, so just use the first one.
+    return list_tests(self._env.devices[0])

[jbudorick, 2015/10/08 14:35:41]

The problem with this is handling the case where listing the test fails on one
device.

[agrieve, 2015/10/08 15:49:29]

Wondered if that was it.

Okay if I change this to add such a comment and just use the first non-None
result? (and add back in sorting)

[jbudorick, 2015/10/08 15:52:45]

Definitely add a comment, and I think that using the first non-None result
should be ok. I debated between that and the current implementation when I wrote
this not that long ago, and I do think the results should be the same on
successful execution.

 
   #override
   def _RunTest(self, device, test):