C  777.579s Main  [FAIL] org.chromium.android_webview.test.AwQuotaManagerBridgeTest#testDeleteOriginWithAppCache:
C  777.579s Main  junit.framework.AssertionFailedError: Criteria not met in allotted time.
C  777.579s Main  	at org.chromium.content.browser.test.util.CriteriaHelper.pollInstrumentationThread(CriteriaHelper.java:74)
C  777.579s Main  	at org.chromium.android_webview.test.AwTestBase.pollInstrumentationThread(AwTestBase.java:499)
C  777.579s Main  	at org.chromium.android_webview.test.AwQuotaManagerBridgeTest.testDeleteOriginWithAppCache(AwQuotaManagerBridgeTest.java:197)
C  777.579s Main  	at java.lang.reflect.Method.invokeNative(Native Method)
C  777.579s Main  	at android.test.InstrumentationTestCase.runMethod(InstrumentationTestCase.java:214)
C  777.579s Main  	at android.test.InstrumentationTestCase.runTest(InstrumentationTestCase.java:199)
C  777.579s Main  	at android.test.ActivityInstrumentationTestCase2.runTest(ActivityInstrumentationTestCase2.java:192)
C  777.580s Main  	at org.chromium.base.test.BaseTestResult.runParameterized(BaseTestResult.java:161)
C  777.580s Main  	at org.chromium.base.test.BaseTestResult.run(BaseTestResult.java:124)
C  777.580s Main  	at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:191)
C  777.580s Main  	at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:176)
C  777.580s Main  	at android.test.InstrumentationTestRunner.onStart(InstrumentationTestRunner.java:554)
C  777.580s Main  	at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1701)

Running this test in a loop exposed other problems. The test server is failing to shutdown :/

I guess you mean ctstestserver. Do you have hush's fix? 

this is the change: https://android-review.googlesource.com/#/c/209838/

No. This is org.chromium.net.test.util.TestWebServer, but it originally was forked from the cts server.

afaict this is not ssl though, so doesn't look related. I'll file another bug for that.

Forked that to  crbug.com/600021 

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

commit 24c4d329de36e9fba9a79f491709428da78ffd34
Author: boliu <boliu@chromium.org>
Date: Fri May 06 23:32:59 2016

aw: Disable quota manager tests

Too flaky. See  crbug.com/609980 .

BUG= 609980 , 599192

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

[modify] https://crrev.com/24c4d329de36e9fba9a79f491709428da78ffd34/android_webview/javatests/src/org/chromium/android_webview/test/AwQuotaManagerBridgeTest.java

Hi Bo,
These tests can be re-enabled now after you've fixed the shutdown deadlock

These tests has nothing to do with the test server shutdown issue. I ran one of these tests overnight to test the test server shutdown fix.

I think the flakes here are all from tests leaving storage data around after it's done, so repeating a single test isn't helping. Not sure.