... on further inspection, this only holds when we run the test activity in the same process as the instrumentation. We don't typically do this (https://codesearch.chromium.org/chromium/src/testing/android/native_test/java/AndroidManifest.xml.jinja2?l=31) but net_unittests, the suite referenced in issue 646085, does. I'm guessing this was an oversight?

Actually, the out-of-process handling could stand to be improved as well.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/cea883202f2e33a6b48b643b3d57221a2ef6187e

commit cea883202f2e33a6b48b643b3d57221a2ef6187e
Author: jbudorick <jbudorick@chromium.org>
Date: Tue Nov 29 14:00:07 2016

[Android] Clean up gtest stdout handling.

including:
 - capturing partial stdout for failed shards
 - removing vestigial fifo support
 - removing on-device results parsing

BUG= 646223 

Review-Url: https://codereview.chromium.org/2514943002
Cr-Commit-Position: refs/heads/master@{#434982}

[modify] https://crrev.com/cea883202f2e33a6b48b643b3d57221a2ef6187e/build/android/pylib/local/device/local_device_gtest_run.py
[modify] https://crrev.com/cea883202f2e33a6b48b643b3d57221a2ef6187e/testing/android/native_test/java/src/org/chromium/native_test/NativeTest.java
[modify] https://crrev.com/cea883202f2e33a6b48b643b3d57221a2ef6187e/testing/android/native_test/java/src/org/chromium/native_test/NativeTestInstrumentationTestRunner.java
[modify] https://crrev.com/cea883202f2e33a6b48b643b3d57221a2ef6187e/testing/android/native_test/native_test_launcher.cc

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/20a1d335f2cf1e97c16e1036bb427a448db84097

commit 20a1d335f2cf1e97c16e1036bb427a448db84097
Author: jbudorick <jbudorick@chromium.org>
Date: Fri Dec 02 05:04:14 2016

[Android] Try harder to run every gtest within each try.

Gtests on Android get sharded into 256-test chunks to mitigate
the latency of spinning up the VM while also allowing for reasonably
balanced sharding across multiple attached devices. This can have
adverse side effects when a test crashes, though, leaving the remaining
tests in a given shard unrun. This is particularly problematic when a
lot of tests crash, with dozens or hundreds of tests failing as
UNKNOWN with no logs.

This CL splits out a separate NOT_RUN status from UNKNOWN to
differentiate between tests that were never run (or that we didn't see
start) and tests that we believe started but for which we were unable to
determine what happened. It then attempts to run any tests that come
back with NOTRUN statuses within each try.

BUG= 646223 

Review-Url: https://codereview.chromium.org/2541093004
Cr-Commit-Position: refs/heads/master@{#435863}

[modify] https://crrev.com/20a1d335f2cf1e97c16e1036bb427a448db84097/build/android/pylib/base/base_test_result.py
[modify] https://crrev.com/20a1d335f2cf1e97c16e1036bb427a448db84097/build/android/pylib/local/device/local_device_gtest_run.py
[modify] https://crrev.com/20a1d335f2cf1e97c16e1036bb427a448db84097/build/android/pylib/local/device/local_device_instrumentation_test_run.py
[modify] https://crrev.com/20a1d335f2cf1e97c16e1036bb427a448db84097/build/android/pylib/local/device/local_device_monkey_test_run.py
[modify] https://crrev.com/20a1d335f2cf1e97c16e1036bb427a448db84097/build/android/pylib/local/device/local_device_test_run.py

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/bee3d3bdd2d7e537cb1341a476bdff18a45334fe

commit bee3d3bdd2d7e537cb1341a476bdff18a45334fe
Author: jbudorick <jbudorick@chromium.org>
Date: Thu Dec 08 21:01:24 2016

[Android] Handle unrun tests as a list rather than a set.

Several bots that subsequently try to rerun an unrun group of test
are left trying to index into a set.

BUG= 646223 

Review-Url: https://codereview.chromium.org/2561153002
Cr-Commit-Position: refs/heads/master@{#437337}

[modify] https://crrev.com/bee3d3bdd2d7e537cb1341a476bdff18a45334fe/build/android/pylib/local/device/local_device_gtest_run.py