diff options
| author | pastarmovj@chromium.org <pastarmovj@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-06-04 14:25:28 +0000 |
|---|---|---|
| committer | pastarmovj@chromium.org <pastarmovj@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-06-04 14:25:28 +0000 |
| commit | efec4f974d787da702c1564518903f3847db42f0 (patch) | |
| tree | 32f17b85f721e5e7198b021ba839719687352928 /chrome/browser/sync/test/integration/sync_test.cc | |
| parent | 10e38b62dec4cd25b15439ea33df703d1285fc88 (diff) | |
| download | chromium_src-efec4f974d787da702c1564518903f3847db42f0.zip chromium_src-efec4f974d787da702c1564518903f3847db42f0.tar.gz chromium_src-efec4f974d787da702c1564518903f3847db42f0.tar.bz2 | |
Introduce maximal wait period for the lockbox to become ready.
We initialize the counter once in the constructor and never reset it because
it makes no sense to ever reset it. As the state will most probably not change
after the timeout has passed once. We still give the callers the chance to
try once but we will not allow second 10s delay to happen until the browser
is restarted.
BUG=chromium-os:31240
TEST=The simples way is to modify cryptohome to always return LOCK_NOT_READY. This is handling exceptional situation which shoud not happen on a daily basis.
TEST=Once we have proper cryptohome mocking we could mock those replies and automate this test.
Review URL: https://chromiumcodereview.appspot.com/10456053
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@140286 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/sync/test/integration/sync_test.cc')
0 files changed, 0 insertions, 0 deletions