[Sync] Set signed in account before AndroidSyncSettings to match test expectations

[Sync] Set signed in account before AndroidSyncSettings to match test expectations

Test expectation is that there is no signed in account at the beginning, and by
the end of setUp test expects mAccount to appear signed in from
AndroidSyncSettings perspective. It is done by calling updateAccount(mAccount)
from setUp(). The issue happens when there is another signed in account
according to ChromeSigninController.getSignedInAccountName, potentially left
from some other test execution.

The fix is to reset signed in account with
ChromeSigninController.setSignedInAccountName before AndroidSyncSettings
initialization.

R=skym@chromium.org
BUG=717960
Review-Url: https://codereview.chromium.org/2884953004
Cr-Commit-Position: refs/heads/master@{#472232}
Committed: https://chromium.googlesource.com/chromium/src/+/7b27ecffa77d8119aa736ecbcb8402256823f956

[pavely, 2017-05-16 20:58:39]

The CQ bit was checked by pavely@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-05-16 21:00:29]

Dry run: CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[skym, 2017-05-16 21:37:06]

lgtm

[pavely, 2017-05-16 21:51:37]

The CQ bit was unchecked by pavely@chromium.org

[pavely, 2017-05-16 21:51:38]

The CQ bit was checked by pavely@chromium.org

[commit-bot: I haz the power, 2017-05-16 21:52:15]

CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-05-16 22:44:38]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1494971498327460, "parent_rev":
"5b36d3236be6e4431ef8307bfbb0aed6187fe24b", "commit_rev":
"7b27ecffa77d8119aa736ecbcb8402256823f956"}

[commit-bot: I haz the power, 2017-05-16 22:44:49]

Description was changed from

==========
[Sync] Set signed in account before AndroidSyncSettings to match test
expectations

Test expectation is that there is no signed in account at the beginning, and by
the end of setUp test expects mAccount to appear signed in from
AndroidSyncSettings perspective. It is done by calling updateAccount(mAccount)
from setUp(). The issue happens when there is another signed in account
according to ChromeSigninController.getSignedInAccountName, potentially left
from some other test execution.

The fix is to reset signed in account with
ChromeSigninController.setSignedInAccountName before AndroidSyncSettings
initialization.

R=skym@chromium.org
BUG=717960
==========

to

==========
[Sync] Set signed in account before AndroidSyncSettings to match test
expectations

Test expectation is that there is no signed in account at the beginning, and by
the end of setUp test expects mAccount to appear signed in from
AndroidSyncSettings perspective. It is done by calling updateAccount(mAccount)
from setUp(). The issue happens when there is another signed in account
according to ChromeSigninController.getSignedInAccountName, potentially left
from some other test execution.

The fix is to reset signed in account with
ChromeSigninController.setSignedInAccountName before AndroidSyncSettings
initialization.

R=skym@chromium.org
BUG=717960

Review-Url: https://codereview.chromium.org/2884953004
Cr-Commit-Position: refs/heads/master@{#472232}
Committed:
https://chromium.googlesource.com/chromium/src/+/7b27ecffa77d8119aa736ecbcb84...
==========

[commit-bot: I haz the power, 2017-05-16 22:44:50]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/7b27ecffa77d8119aa736ecbcb84...