summaryrefslogtreecommitdiffstats
path: root/third_party/sudden_motion_sensor
diff options
context:
space:
mode:
authorphoglund@chromium.org <phoglund@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2014-05-06 09:42:35 +0000
committerphoglund@chromium.org <phoglund@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2014-05-06 09:42:35 +0000
commit95092d6adcfda453c8bcce4ed835ea524ee60a5e (patch)
treefe1219ef8ad7dedad4409085856dda2d6f667270 /third_party/sudden_motion_sensor
parent65290011287a21557f2423b81f243a5039d7cc2f (diff)
downloadchromium_src-95092d6adcfda453c8bcce4ed835ea524ee60a5e.zip
chromium_src-95092d6adcfda453c8bcce4ed835ea524ee60a5e.tar.gz
chromium_src-95092d6adcfda453c8bcce4ed835ea524ee60a5e.tar.bz2
Revert 267897 "Revert 267858 "Working around IO thread chrashes ..."
> Revert 267858 "Working around IO thread chrashes for WebRTC test..." > > Android browser tests still failing at http://chromegw/i/client.webrtc/waterfall > > > 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 > > > > Review URL: https://codereview.chromium.org/251323002 > > TBR=phoglund@chromium.org > > Review URL: https://codereview.chromium.org/262773014 Appears the revert may have been incorrect; speculative re-land. TBR=niklase@chromium.org Review URL: https://codereview.chromium.org/262173013 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@268474 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'third_party/sudden_motion_sensor')
0 files changed, 0 insertions, 0 deletions