diff options
| author | cjhopman@chromium.org <cjhopman@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-01-29 00:50:36 +0000 |
|---|---|---|
| committer | cjhopman@chromium.org <cjhopman@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-01-29 00:50:36 +0000 |
| commit | b3c1b3b66d1c720172e731d1bfc44cfb44c992a3 (patch) | |
| tree | d8c9a1fc0a0fa78a9362ec0727d8d41fb0e11138 /content/public/browser/render_process_host.h | |
| parent | f54329e5d6a76858c67869e678f9462a964632b7 (diff) | |
| download | chromium_src-b3c1b3b66d1c720172e731d1bfc44cfb44c992a3.zip chromium_src-b3c1b3b66d1c720172e731d1bfc44cfb44c992a3.tar.gz chromium_src-b3c1b3b66d1c720172e731d1bfc44cfb44c992a3.tar.bz2 | |
Revert of [Android] Re-enable content_browsertests on main waterfall. (https://codereview.chromium.org/132403005/)
Reason for revert:
content_browsertests have been crashy and flaky since being re-enabled.
Looks like they crashing on shutdown, but I'm not sure.
Failed:
http://build.chromium.org/p/chromium.linux/builders/Android%20Tests/builds/11552
http://build.chromium.org/p/chromium.linux/builders/Android%20Tests/builds/11554
On this one, content_browsertests crashed but still passed. This caused INJECT_EVENTS exceptions in later tests.
http://build.chromium.org/p/chromium.linux/builders/Android%20Tests%20%28dbg%29/builds/18163
We see the same thing downstream.
Original issue's description:
> [Android] Re-enable content_browsertests on main waterfall.
>
> There's enough infra capacity now.
>
> BUG=
> R=navabi@chromium.org, navabi@google.com
>
> Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=247341
TBR=navabi@chromium.org,navabi@google.com,frankf@chromium.org
NOTREECHECKS=true
NOTRY=true
BUG=
Review URL: https://codereview.chromium.org/135363005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@247547 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'content/public/browser/render_process_host.h')
0 files changed, 0 insertions, 0 deletions