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

commit 73d289c135fe05b623476d753cfadf4bde1a010c
Author: mvanouwerkerk <mvanouwerkerk@chromium.org>
Date: Mon Mar 07 14:20:51 2016

Mark some cronet instrumentation tests flaky.

BUG= 592444 
TBR=mef
NOTRY=true

Review URL: https://codereview.chromium.org/1773613002

Cr-Commit-Position: refs/heads/master@{#379553}

[modify] https://crrev.com/73d289c135fe05b623476d753cfadf4bde1a010c/components/cronet/android/sample/javatests/src/org/chromium/cronet_sample_apk/CronetSampleTest.java
[modify] https://crrev.com/73d289c135fe05b623476d753cfadf4bde1a010c/components/cronet/android/test/javatests/src/org/chromium/net/CronetUrlRequestContextTest.java
[modify] https://crrev.com/73d289c135fe05b623476d753cfadf4bde1a010c/components/cronet/android/test/javatests/src/org/chromium/net/CronetUrlRequestTest.java

We need to figure out whether this flakiness is DRP-specific, or across the board.

Upping the priority here. I just spent ~ 30min running CronetSampleTest and didn't know why there was no test ran -- The only test that it has is disabled. We need to figure out why these tests are flaky. Otherwise the technical debt will just accumulate. I filed  Issue 635021  to investigate that one.

CronetUrlRequestContextTest#testRequestFinishedListenerFailedRequest (now RequestFinishedInfoTest#testRequestFinishedListenerFailedRequest) has been fixed. The others are all still marked flaky or disabled.

Great. Thanks Miriam. I will close this one and file separate ones for each. That way, hopefully we will get them tackled sooner.