Relanding "Multiprocess test client: Android child process launcher rework."

Reland of new multiprocess test client process launcher.
Changed the way the native main function is invoked so that the main stub
is not required anymore. Launching in the sub-process is now done from Java
by calling into the new MainRunner class whose JNI code is in the same
module as the one used to start the test natively and is already linked
with main().

BUG=666356
Original issue's description:
> Multiprocess test client: Android child process launcher rework.
> 
> Changing the way test start child processese on Android.
> Forking natively should not be used on Andoid, instead child processes
> should be started through the Android framework, which requires going
> to Java and using Android services.
> 
> For that we introduce the MultiprocessTestClientLauncher java class
> which starts a service in a new process. We provide several
> MultiprocessTestClientService service classes to ensure we can have
> multiple child processes.
> File descriptor are passed from the parent to the child process as
> Parcelable, and we use the GlobalDescriptors class to register them.
> 
> TEST=Run the mojo_system_unittests
> BUG=666356
> Review-Url: https://codereview.chromium.org/2549363004
> Cr-Commit-Position: refs/heads/master@{#441799}
> Committed: https://chromium.googlesource.com/chromium/src/+/5513e4622febbc838dfebddb51347ab797747836

Review-Url: https://codereview.chromium.org/2611323002
Cr-Commit-Position: refs/heads/master@{#442477}
Committed: https://chromium.googlesource.com/chromium/src/+/f4462a35264c65c6e554d22b00bb76c423c2e703

[Jay Civelli, 2017-01-07 05:07:11]

Description was changed from

==========
Revert "Revert of Multiprocess test client: Android child process launcher
rework. (patchset #21 id:400001 of https://codereview.chromium.org/2549363004/
)"

This reverts commit 8f2c67087919621e412ac9a5e82a2e719de80362.

BUG=
==========

to

==========
Revert "Revert of Multiprocess test client: Android child process launcher
rework"

Reland of new multiprocess test client process launcher.
The non component build was fixed.

BUG=666356

Original issue's description:
> Multiprocess test client: Android child process launcher rework.
> 
> Changing the way test start child processese on Android.
> Forking natively should not be used on Andoid, instead child processes
> should be started through the Android framework, which requires going
> to Java and using Android services.
> 
> For that we introduce the MultiprocessTestClientLauncher java class
> which starts a service in a new process. We provide several
> MultiprocessTestClientService service classes to ensure we can have
> multiple child processes.
> File descriptor are passed from the parent to the child process as
> Parcelable, and we use the GlobalDescriptors class to register them.
> 
> TEST=Run the mojo_system_unittests
> BUG=666356
> Review-Url: https://codereview.chromium.org/2549363004
> Cr-Commit-Position: refs/heads/master@{#441799}
> Committed:
https://chromium.googlesource.com/chromium/src/+/5513e4622febbc838dfebddb5134...
==========

[Jay Civelli, 2017-01-07 05:07:30]

The CQ bit was checked by jcivelli@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-01-07 05:07:38]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-01-07 05:17:08]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-01-07 05:17:08]

Dry run: Try jobs failed on following builders:
  cast_shell_android on master.tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/cast_shell_a...)

[Jay Civelli, 2017-01-07 05:38:25]

The CQ bit was checked by jcivelli@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-01-07 05:38:40]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-01-07 06:56:55]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-01-07 06:56:56]

Dry run: Try jobs failed on following builders:
  android_n5x_swarming_rel on master.tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/android_n5x_...)

[Jay Civelli, 2017-01-09 16:34:07]

Description was changed from

==========
Revert "Revert of Multiprocess test client: Android child process launcher
rework"

Reland of new multiprocess test client process launcher.
The non component build was fixed.

BUG=666356

Original issue's description:
> Multiprocess test client: Android child process launcher rework.
> 
> Changing the way test start child processese on Android.
> Forking natively should not be used on Andoid, instead child processes
> should be started through the Android framework, which requires going
> to Java and using Android services.
> 
> For that we introduce the MultiprocessTestClientLauncher java class
> which starts a service in a new process. We provide several
> MultiprocessTestClientService service classes to ensure we can have
> multiple child processes.
> File descriptor are passed from the parent to the child process as
> Parcelable, and we use the GlobalDescriptors class to register them.
> 
> TEST=Run the mojo_system_unittests
> BUG=666356
> Review-Url: https://codereview.chromium.org/2549363004
> Cr-Commit-Position: refs/heads/master@{#441799}
> Committed:
https://chromium.googlesource.com/chromium/src/+/5513e4622febbc838dfebddb5134...
==========

to

==========
Reland of new multiprocess test client process launcher.
The non component build was fixed.

BUG=666356

Original issue's description:
> Multiprocess test client: Android child process launcher rework.
> 
> Changing the way test start child processese on Android.
> Forking natively should not be used on Andoid, instead child processes
> should be started through the Android framework, which requires going
> to Java and using Android services.
> 
> For that we introduce the MultiprocessTestClientLauncher java class
> which starts a service in a new process. We provide several
> MultiprocessTestClientService service classes to ensure we can have
> multiple child processes.
> File descriptor are passed from the parent to the child process as
> Parcelable, and we use the GlobalDescriptors class to register them.
> 
> TEST=Run the mojo_system_unittests
> BUG=666356
> Review-Url: https://codereview.chromium.org/2549363004
> Cr-Commit-Position: refs/heads/master@{#441799}
> Committed:
https://chromium.googlesource.com/chromium/src/+/5513e4622febbc838dfebddb5134...
==========

[Jay Civelli, 2017-01-09 17:44:45]

Description was changed from

==========
Reland of new multiprocess test client process launcher.
The non component build was fixed.

BUG=666356

Original issue's description:
> Multiprocess test client: Android child process launcher rework.
> 
> Changing the way test start child processese on Android.
> Forking natively should not be used on Andoid, instead child processes
> should be started through the Android framework, which requires going
> to Java and using Android services.
> 
> For that we introduce the MultiprocessTestClientLauncher java class
> which starts a service in a new process. We provide several
> MultiprocessTestClientService service classes to ensure we can have
> multiple child processes.
> File descriptor are passed from the parent to the child process as
> Parcelable, and we use the GlobalDescriptors class to register them.
> 
> TEST=Run the mojo_system_unittests
> BUG=666356
> Review-Url: https://codereview.chromium.org/2549363004
> Cr-Commit-Position: refs/heads/master@{#441799}
> Committed:
https://chromium.googlesource.com/chromium/src/+/5513e4622febbc838dfebddb5134...
==========

to

==========
Reland of new multiprocess test client process launcher.
Changed the way the native main function is invoked so that the main stub
is not required anymore. Launching in the sub-process is now done from Java
by calling into the new MainRunner class whose JNI code is in the same
module as the one used to start the test natively and is already linked
with main().

BUG=666356

Original issue's description:
> Multiprocess test client: Android child process launcher rework.
> 
> Changing the way test start child processese on Android.
> Forking natively should not be used on Andoid, instead child processes
> should be started through the Android framework, which requires going
> to Java and using Android services.
> 
> For that we introduce the MultiprocessTestClientLauncher java class
> which starts a service in a new process. We provide several
> MultiprocessTestClientService service classes to ensure we can have
> multiple child processes.
> File descriptor are passed from the parent to the child process as
> Parcelable, and we use the GlobalDescriptors class to register them.
> 
> TEST=Run the mojo_system_unittests
> BUG=666356
> Review-Url: https://codereview.chromium.org/2549363004
> Cr-Commit-Position: refs/heads/master@{#441799}
> Committed:
https://chromium.googlesource.com/chromium/src/+/5513e4622febbc838dfebddb5134...
==========

[Jay Civelli, 2017-01-09 19:05:40]

jcivelli@chromium.org changed reviewers:
+ boliu@chromium.org, dcheng@chromium.org, eroman@chromium.org,
nyquist@chromium.org, rockot@chromium.org

[Jay Civelli, 2017-01-09 19:08:47]

jcivelli@chromium.org changed reviewers:
+ dpranke@chromium.org, jbudorick@chromium.org

[Jay Civelli, 2017-01-09 19:13:43]

Had to change the way we call the main() function from the child process so the
non component build links, which made actually things cleaner (no need for a
main_stub anymore).
Patch set 1 is the original patch, so you can easily see the new changes by
looking at the delta to that patch set.

[dcheng, 2017-01-09 19:24:35]

base lgtm

[boliu, 2017-01-09 19:32:06]

android_webview rs lgtm, no change from last time :)

[Dirk Pranke, 2017-01-09 20:12:00]

//testing still lgtm.

[Jay Civelli, 2017-01-09 20:43:06]

jcivelli@chromium.org changed reviewers:
- eroman@chromium.org

[jbudorick, 2017-01-09 21:00:13]

lgtm

[Ken Rockot(use gerrit already), 2017-01-09 21:01:12]

rs lgtm

[nyquist, 2017-01-10 00:25:59]

lgtm

https://codereview.chromium.org/2611323002/diff/10047/testing/android/native_...
File
testing/android/native_test/java/src/org/chromium/native_test/MainRunner.java
(right):

https://codereview.chromium.org/2611323002/diff/10047/testing/android/native_...
testing/android/native_test/java/src/org/chromium/native_test/MainRunner.java:16:
public class MainRunner {
Nit: This utility class with only static methods should be final.

[Jay Civelli, 2017-01-10 00:46:37]

The CQ bit was checked by jcivelli@chromium.org

[Jay Civelli, 2017-01-10 00:46:37]

The patchset sent to the CQ was uploaded after l-g-t-m from rockot@chromium.org,
dpranke@chromium.org, jbudorick@chromium.org, boliu@chromium.org,
dcheng@chromium.org, nyquist@chromium.org
Link to the patchset: https://codereview.chromium.org/2611323002/#ps50001
(title: "Addressed nyquist@'s comment + sync")

[Jay Civelli, 2017-01-10 00:46:46]

https://codereview.chromium.org/2611323002/diff/10047/testing/android/native_...
File
testing/android/native_test/java/src/org/chromium/native_test/MainRunner.java
(right):

https://codereview.chromium.org/2611323002/diff/10047/testing/android/native_...
testing/android/native_test/java/src/org/chromium/native_test/MainRunner.java:16:
public class MainRunner {
On 2017/01/10 00:25:59, nyquist wrote:
> Nit: This utility class with only static methods should be final.

Done.

[commit-bot: I haz the power, 2017-01-10 00:47:53]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-01-10 02:50:43]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-01-10 02:50:44]

Try jobs failed on following builders:
  chromeos_amd64-generic_chromium_compile_only_ng on
master.tryserver.chromium.linux (JOB_TIMED_OUT, no build URL)

[Jay Civelli, 2017-01-10 04:29:10]

The CQ bit was checked by jcivelli@chromium.org

[commit-bot: I haz the power, 2017-01-10 04:30:14]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-01-10 04:46:03]

CQ is committing da patch.

Bot data: {"patchset_id": 50001, "attempt_start_ts": 1484022550158750,
"parent_rev": "4376a2a8722814a5f3feaaa5f7b335beb5ad29df", "commit_rev":
"f4462a35264c65c6e554d22b00bb76c423c2e703"}

[commit-bot: I haz the power, 2017-01-10 04:46:43]

Description was changed from

==========
Reland of new multiprocess test client process launcher.
Changed the way the native main function is invoked so that the main stub
is not required anymore. Launching in the sub-process is now done from Java
by calling into the new MainRunner class whose JNI code is in the same
module as the one used to start the test natively and is already linked
with main().

BUG=666356

Original issue's description:
> Multiprocess test client: Android child process launcher rework.
> 
> Changing the way test start child processese on Android.
> Forking natively should not be used on Andoid, instead child processes
> should be started through the Android framework, which requires going
> to Java and using Android services.
> 
> For that we introduce the MultiprocessTestClientLauncher java class
> which starts a service in a new process. We provide several
> MultiprocessTestClientService service classes to ensure we can have
> multiple child processes.
> File descriptor are passed from the parent to the child process as
> Parcelable, and we use the GlobalDescriptors class to register them.
> 
> TEST=Run the mojo_system_unittests
> BUG=666356
> Review-Url: https://codereview.chromium.org/2549363004
> Cr-Commit-Position: refs/heads/master@{#441799}
> Committed:
https://chromium.googlesource.com/chromium/src/+/5513e4622febbc838dfebddb5134...
==========

to

==========
Reland of new multiprocess test client process launcher.
Changed the way the native main function is invoked so that the main stub
is not required anymore. Launching in the sub-process is now done from Java
by calling into the new MainRunner class whose JNI code is in the same
module as the one used to start the test natively and is already linked
with main().

BUG=666356

Original issue's description:
> Multiprocess test client: Android child process launcher rework.
> 
> Changing the way test start child processese on Android.
> Forking natively should not be used on Andoid, instead child processes
> should be started through the Android framework, which requires going
> to Java and using Android services.
> 
> For that we introduce the MultiprocessTestClientLauncher java class
> which starts a service in a new process. We provide several
> MultiprocessTestClientService service classes to ensure we can have
> multiple child processes.
> File descriptor are passed from the parent to the child process as
> Parcelable, and we use the GlobalDescriptors class to register them.
> 
> TEST=Run the mojo_system_unittests
> BUG=666356
> Review-Url: https://codereview.chromium.org/2549363004
> Cr-Commit-Position: refs/heads/master@{#441799}
> Committed:
https://chromium.googlesource.com/chromium/src/+/5513e4622febbc838dfebddb5134...

Review-Url: https://codereview.chromium.org/2611323002
Cr-Commit-Position: refs/heads/master@{#442477}
Committed:
https://chromium.googlesource.com/chromium/src/+/f4462a35264c65c6e554d22b00bb...
==========

[commit-bot: I haz the power, 2017-01-10 04:46:45]

Committed patchset #4 (id:50001) as
https://chromium.googlesource.com/chromium/src/+/f4462a35264c65c6e554d22b00bb...