Sync android-chrome revision along with chromium on android-chrome platform.

Sync android-chrome revision along with chromium on android-chrome platform.

android-chrome revision is overwritten with TOT revision when we sync only
chromium revision. This causes inconsistency between android-chrome and chromium
revisions that we want to bisect. Therefore we pass android-chrome revision along with chromium
revision to make sure we are bisect chromium on proper android-chrome revision.

BUG=447348
NOTRY=true

Committed: https://crrev.com/a2fe607ce642aac9ce063d84ee79b92ff256e436
Cr-Commit-Position: refs/heads/master@{#310681}

[prasadv, 2015-01-08 22:51:34]

prasadv@chromium.org changed reviewers:
+ qyearsley@chromium.org

[qyearsley, 2015-01-09 00:46:46]

LGTM, looks like my comments from before were addressed.

I'm still wondering whether RunGClientAndSync (and other others) could have
tests added/updated?
Two general types of test you could potentially have:
 1) mocking out subprocess.call, just checking which command is being executed.
 2) actually running the gclient or git commands.
The former might be slightly easier. WDYT?

[qyearsley, 2015-01-09 02:34:56]

On 2015/01/09 02:34:02, prasadv wrote:

Test lgtm :-)

[prasadv, 2015-01-09 02:35:10]

The CQ bit was checked by prasadv@chromium.org

[commit-bot: I haz the power, 2015-01-09 02:36:14]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/800143003/20001

[commit-bot: I haz the power, 2015-01-09 02:37:59]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-01-09 02:39:20]

Patchset 2 (id:??) landed as
https://crrev.com/a2fe607ce642aac9ce063d84ee79b92ff256e436
Cr-Commit-Position: refs/heads/master@{#310681}