ProfileSyncServiceHarness: don't sign in if already signed in
Changing the refresh token causes Sync (ServerConnectionManager in particular) to mark the current access token as invalid. Since tests typically always hand out the same access token string, any new access token acquired later would also be considered invalid. This was exposed by https://crrev.com/c/1148392, but the problem existed all along. Bug: 856179 Change-Id: I47e695e2415252281404b4e6e6170667ecf8180d Reviewed-on: https://chromium-review.googlesource.com/1156595Reviewed-by:Mikel Astiz <mastiz@chromium.org> Commit-Queue: Marc Treib <treib@chromium.org> Cr-Commit-Position: refs/heads/master@{#579410}
Showing
Please register or sign in to comment