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

commit f7461118211ccac06090eb8b70d25c52aa314a1b
Author: jbudorick <jbudorick@chromium.org>
Date: Fri May 27 04:30:49 2016

[Android] Fix unknown handling in gtest_test_instance.

BUG= 615086 ,615291
TBR=dewittj@chromium.org

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

[modify] https://crrev.com/f7461118211ccac06090eb8b70d25c52aa314a1b/build/android/pylib/gtest/gtest_test_instance.py
[modify] https://crrev.com/f7461118211ccac06090eb8b70d25c52aa314a1b/build/android/pylib/gtest/gtest_test_instance_test.py
[modify] https://crrev.com/f7461118211ccac06090eb8b70d25c52aa314a1b/build/android/pylib/local/device/local_device_gtest_run.py
[modify] https://crrev.com/f7461118211ccac06090eb8b70d25c52aa314a1b/build/android/pylib/remote/device/remote_device_gtest_run.py
[modify] https://crrev.com/f7461118211ccac06090eb8b70d25c52aa314a1b/content/browser/download/mhtml_generation_browsertest.cc

I've been seeing this same problem with other tests too. FindRequestManagerTest.* tests fail on this DCHECK on the linux_android_rel_ng trybot, and ONLY on that trybot, and only sometimes. They were disabled for Android because of it. I haven't been able to reproduce the problem locally no matter what I try (I've tried lots of different configurations and different Android devices).

yosin@ has been looking into this as well.

After talking to yosin@, this is suspected to be a problem with the bot's config for ICU.

Based on #6, I think someone else is likely to be a better owner of the root cause than me.  Paul, is that someone you?

No, not me. I looked into this a bit just because I had a test that was failing but I still really don't k ow what's going on here. yosin@ owns the bit of code where the DCHECK is hit, so perhaps he would be a good owner. 

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

commit cc9a00f96ebe2ec23c1626e5e42de5313e968ef7
Author: paulmeyer <paulmeyer@chromium.org>
Date: Wed Jul 06 13:44:27 2016

Small optimization in disabling tests on Android Release in find_request_manager_browsertest.cc.

This patch removes the need to add MAYBE lines for nearly every test that goes into find_request_manager_browsertest.cc. It does this by defining a MAYBE() function instead of MAYBE/DISABLED definitions for every test name.

BUG=615291

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

[modify] https://crrev.com/cc9a00f96ebe2ec23c1626e5e42de5313e968ef7/content/browser/find_request_manager_browsertest.cc

 Issue 657331  has been merged into this issue.

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

commit 65fee8192a9f0c1c1e1c8b8f99b6e046441e71e6
Author: torne <torne@chromium.org>
Date: Tue Oct 25 12:09:03 2016

Disable FindRequestManager tests on android debug also.

Tests were already disabled for release; disable for debug as well since
the issue doesn't seem to be debug/release specific (possibly test
device config is the issue?)

BUG=615291
TBR=paulmeyer@chromium.org

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

[modify] https://crrev.com/65fee8192a9f0c1c1e1c8b8f99b6e046441e71e6/content/browser/find_request_manager_browsertest.cc

If this is really a Pri-1, find an owner and update the priority.

This is the result of a bulk edit that moved high priority available bugs to a lower priority in an attempt to be more honest with bug filers.

yosin@, did you ever determine the cause or confirm the theory in #6?