Issue 689298  has been merged into this issue.

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

commit 29785ff5f0981c50c14d2df00a099be628641a9e
Author: michaelbai <michaelbai@chromium.org>
Date: Wed Feb 08 02:09:38 2017

Wait 5 times for render process crash callback

The test is flaky on some device because of timeout, wait multiple
times for callback

BUG= 689292 

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

[modify] https://crrev.com/29785ff5f0981c50c14d2df00a099be628641a9e/android_webview/javatests/src/org/chromium/android_webview/test/AwContentsClientOnRenderProcessGoneTest.java

Detected 5 new flakes for test/step "org.chromium.android_webview.test.AwContentsClientOnRenderProcessGoneTest#testOnRenderProcessCrash". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNybQsSBUZsYWtlImJvcmcuY2hyb21pdW0uYW5kcm9pZF93ZWJ2aWV3LnRlc3QuQXdDb250ZW50c0NsaWVudE9uUmVuZGVyUHJvY2Vzc0dvbmVUZXN0I3Rlc3RPblJlbmRlclByb2Nlc3NDcmFzaAw. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Sheriff Bug Queue (unless already there).

Detected 9 new flakes for test/step "org.chromium.android_webview.test.AwContentsClientOnRenderProcessGoneTest#testOnRenderProcessCrash". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNybQsSBUZsYWtlImJvcmcuY2hyb21pdW0uYW5kcm9pZF93ZWJ2aWV3LnRlc3QuQXdDb250ZW50c0NsaWVudE9uUmVuZGVyUHJvY2Vzc0dvbmVUZXN0I3Rlc3RPblJlbmRlclByb2Nlc3NDcmFzaAw. This message was posted automatically by the chromium-try-flakes app.

Looks like this is still showing up. @michaelbai: Any ideas what might be going on?

It seemed system crash dialog prevent test running, I will see if there is a way to disable the system crash dialog.

Device(07406225003b76cb) 02-10 15:24:17.299   184   184 I DEBUG   :     777dc648 78232314 f04f07db f88d0307 f04f303d
Device(07406225003b76cb) 02-10 15:24:19.299   814  1075 E NativeCrashListener: Exception dealing with report
Device(07406225003b76cb) 02-10 15:24:19.299   814  1075 E NativeCrashListener: libcore.io.ErrnoException: read failed: EAGAIN (Try again)
Device(07406225003b76cb) 02-10 15:24:19.299   814  1075 E NativeCrashListener:  at libcore.io.Posix.readBytes(Native Method)
Device(07406225003b76cb) 02-10 15:24:19.299   814  1075 E NativeCrashListener:  at libcore.io.Posix.read(Posix.java:128)
Device(07406225003b76cb) 02-10 15:24:19.299   814  1075 E NativeCrashListener:  at libcore.io.BlockGuardOs.read(BlockGuardOs.java:149)
Device(07406225003b76cb) 02-10 15:24:19.299   814  1075 E NativeCrashListener:  at com.android.server.am.NativeCrashListener.consumeNativeCrashData(Nat\
iveCrashListener.java:240)
Device(07406225003b76cb) 02-10 15:24:19.299   814  1075 E NativeCrashListener:  at com.android.server.am.NativeCrashListener.run(NativeCrashListener.ja\
va:138)
Device(07406225003b76cb) 02-10 15:24:19.820   814   906 W ProcessCpuTracker: Skipping unknown process pid 5082
Device(07406225003b76cb) 02-10 15:24:41.919   814   823 W JavaBinder: Binder has been finalized when calling linkToDeath() with recip=0x1d200005)
Device(07406225003b76cb) 02-10 15:24:41.929   814  1260 D dalvikvm: GC_FOR_ALLOC freed 1954K, 16% free 23988K/28464K, paused 34ms, total 37ms
Device(07406225003b76cb) 02-10 15:24:41.959  5000  5015 D dalvikvm: GC_EXPLICIT freed 132K, 3% free 17136K/17556K, paused 1ms+7ms, total 22ms
Device(07406225003b76cb) 02-10 15:24:41.969  5000  5015 D dalvikvm: GC_EXPLICIT freed 1K, 3% free 17134K/17556K, paused 1ms+2ms, total 14ms
Device(07406225003b76cb) 02-10 15:24:41.979  5000  5015 E TestStatusListener: Error while running testOnRenderProcessCrash(org.chromium.android_webview\
.test.AwContentsClientOnRenderProcessGoneTest)

oh oh, yes!

See my CLs in  crbug.com/680775 

But in the mean time, disable this test while fix is pending

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

commit 11779b13c335bea1ebe2d09629be2988578dd4b0
Author: michaelbai <michaelbai@chromium.org>
Date: Fri Feb 10 19:47:59 2017

Disable testOnRenderProcessCrash

BUG= 689292 

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

[modify] https://crrev.com/11779b13c335bea1ebe2d09629be2988578dd4b0/android_webview/javatests/src/org/chromium/android_webview/test/AwContentsClientOnRenderProcessGoneTest.java

> See my CLs in  crbug.com/680775 

Perhaps that's not very clear.. In the child process, in java, do "Process.killProcess(Process.myPid());". That should not throw up any dialog as that's a sigkill.

Suppressing the dialog in native crash (which usually doesn't generate sigkill) is more involved, and I don't recommend doing that.

Doesn't look like sheriff action is required.

SIGKILL is not an issue, there is another test uses SIGKILL to kill render process, it works well.

This test is for render crash which is killed by SIGSEGV, it seemed that the device wait for a debugger to attach on failed device.

Detected 7 new flakes for test/step "org.chromium.android_webview.test.AwContentsClientOnRenderProcessGoneTest#testOnRenderProcessCrash". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNybQsSBUZsYWtlImJvcmcuY2hyb21pdW0uYW5kcm9pZF93ZWJ2aWV3LnRlc3QuQXdDb250ZW50c0NsaWVudE9uUmVuZGVyUHJvY2Vzc0dvbmVUZXN0I3Rlc3RPblJlbmRlclByb2Nlc3NDcmFzaAw. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Sheriff Bug Queue (unless already there).