Working around IO thread chrashes for WebRTC tests on Android.

Working around IO thread chrashes for WebRTC tests on Android.

Because the content_browsertests tearDown logic is broken with respect
to threading on Android, we here work around the problem by sleeping in
the tearDown to give the IO thread time to finish its work. This will
lengthen the execution time of the tests but hopefully make the tests
stable enough to last us until the Clank team finds time to rewrite the
tearDown logic.

BUG=362852
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=267858

[phoglund_chromium, 2014-04-29 14:41:21]

Hmm, I'm a bit confused. The run succeeded locally (it had been failing earlier)
but I now realize that I had misnamed the TearDown method which means my fix
wasn't executing. I'm going to experiment a bit more with this one.

[phoglund_chromium, 2014-04-30 13:06:43]

This seems to help anecdotally. It's ugly but I don't have a better idea (and
running without peerconnection tests for 2+ months on Android seems worse).
Running with 2 seconds I saw crashes, but with 5 I couldn't see any. This could
be worth trying. We could disable half of the browser tests and just run the /1
variants to compensate for the extra five seconds per test case.

[tommi (sloooow) - chröme, 2014-05-01 10:30:41]

lgtm - rather ugly hack but I agree with you that it's better to have the tests
running than not at all.

[phoglund_chromium, 2014-05-02 08:06:56]

The CQ bit was checked by phoglund@chromium.org

[commit-bot: I haz the power, 2014-05-02 08:07:07]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/phoglund@chromium.org/251323002/20001

[commit-bot: I haz the power, 2014-05-02 08:22:02]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-05-02 08:22:02]

Try jobs failed on following builders:
  mac_chromium_rel on tryserver.chromium

[phoglund_chromium, 2014-05-02 09:21:42]

The CQ bit was checked by phoglund@chromium.org

[commit-bot: I haz the power, 2014-05-02 09:22:16]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/phoglund@chromium.org/251323002/20001

[commit-bot: I haz the power, 2014-05-02 17:53:52]

Change committed as 267858