Revert of PrecacheFetcher::CancelPrecaching should run in the main UI thread

Revert of PrecacheFetcher::CancelPrecaching should run in the main UI thread (patchset #4 id:60001 of https://codereview.chromium.org/2137593002/ )

Reason for revert:
Android Test (dbg) has turned red, with failures:
C  860.211s Main  [  FAILED  ] org.chromium.chrome.browser.precache.PrecacheControllerTest#testDeviceStateChangeCancels
C  860.211s Main  [  FAILED  ] org.chromium.chrome.browser.precache.PrecacheControllerTest#testTimeoutCancelsPrecaching
C  860.211s Main  [  FAILED  ] org.chromium.chrome.browser.precache.PrecacheControllerTest#testTimeoutDoesNotCancelIfNotPrecaching (UNKNOWN)
C  860.211s Main  [  FAILED  ] org.chromium.chrome.browser.precache.PrecacheLauncherTest#testUpdateEnabled_Disabled_ThenEnabled (UNKNOWN)
C  860.211s Main  [  FAILED  ] org.chromium.chrome.browser.precache.PrecacheLauncherTest#testUpdateEnabled_SyncNotReady_ThenEnabled (UNKNOWN)

 Link to bot:

https://uberchromegw.corp.google.com/i/chromium.linux/builders/Android%20Tests%20(dbg)

Original issue's description:
> PrecacheFetcher::CancelPrecaching should run in the main UI thread
>
> Reducing the possibilities of crash in CancelPrecaching.
>
> BUG=619111
>
> Committed: https://crrev.com/28e7a0cc33dafc8719c4b9c740d79a47ff90f067
> Cr-Commit-Position: refs/heads/master@{#404792}

TBR=sclittle@chromium.org,rajendrant@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=619111
Committed: https://crrev.com/285187208715fc68c217d4a7d237f96277fce50c
Cr-Commit-Position: refs/heads/master@{#404810}

[picksi1, 2016-07-12 14:25:24]

The CQ bit was checked by picksi@chromium.org

[picksi1, 2016-07-12 14:25:25]

Created Revert of PrecacheFetcher::CancelPrecaching should run in the main UI
thread

[commit-bot: I haz the power, 2016-07-12 14:26:23]

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, 2016-07-12 14:26:24]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-07-12 14:26:25]

No L-G-T-M from a valid reviewer yet. 
CQ run can only be started by full committers or once the patch has
received an L-G-T-M from a full committer.
Even if an L-G-T-M may have been provided, it was from a non-committer,
_not_ a full super star committer.
See http://www.chromium.org/getting-involved/become-a-committer
Note that this has nothing to do with OWNERS files.

[alex clarke (OOO till 29th), 2016-07-12 14:28:49]

alexclarke@chromium.org changed reviewers:
+ alexclarke@chromium.org

[alex clarke (OOO till 29th), 2016-07-12 14:28:49]

lgtm

[picksi1, 2016-07-12 14:32:41]

The CQ bit was checked by picksi@chromium.org

[commit-bot: I haz the power, 2016-07-12 14:33:49]

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, 2016-07-12 14:34:40]

Description was changed from

==========
Revert of PrecacheFetcher::CancelPrecaching should run in the main UI thread
(patchset #4 id:60001 of https://codereview.chromium.org/2137593002/ )

Reason for revert:
Android Test (dbg) has turned red, with failures:
C  860.211s Main  [  FAILED  ]
org.chromium.chrome.browser.precache.PrecacheControllerTest#testDeviceStateChangeCancels
C  860.211s Main  [  FAILED  ]
org.chromium.chrome.browser.precache.PrecacheControllerTest#testTimeoutCancelsPrecaching
C  860.211s Main  [  FAILED  ]
org.chromium.chrome.browser.precache.PrecacheControllerTest#testTimeoutDoesNotCancelIfNotPrecaching
(UNKNOWN)
C  860.211s Main  [  FAILED  ]
org.chromium.chrome.browser.precache.PrecacheLauncherTest#testUpdateEnabled_Disabled_ThenEnabled
(UNKNOWN)
C  860.211s Main  [  FAILED  ]
org.chromium.chrome.browser.precache.PrecacheLauncherTest#testUpdateEnabled_SyncNotReady_ThenEnabled
(UNKNOWN)

 Link to bot:

https://uberchromegw.corp.google.com/i/chromium.linux/builders/Android%20Test...


Original issue's description:
> PrecacheFetcher::CancelPrecaching should run in the main UI thread
> 
> Reducing the possibilities of crash in CancelPrecaching.
> 
> BUG=619111
> 
> Committed: https://crrev.com/28e7a0cc33dafc8719c4b9c740d79a47ff90f067
> Cr-Commit-Position: refs/heads/master@{#404792}

TBR=sclittle@chromium.org,rajendrant@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=619111
==========

to

==========
Revert of PrecacheFetcher::CancelPrecaching should run in the main UI thread
(patchset #4 id:60001 of https://codereview.chromium.org/2137593002/ )

Reason for revert:
Android Test (dbg) has turned red, with failures:
C  860.211s Main  [  FAILED  ]
org.chromium.chrome.browser.precache.PrecacheControllerTest#testDeviceStateChangeCancels
C  860.211s Main  [  FAILED  ]
org.chromium.chrome.browser.precache.PrecacheControllerTest#testTimeoutCancelsPrecaching
C  860.211s Main  [  FAILED  ]
org.chromium.chrome.browser.precache.PrecacheControllerTest#testTimeoutDoesNotCancelIfNotPrecaching
(UNKNOWN)
C  860.211s Main  [  FAILED  ]
org.chromium.chrome.browser.precache.PrecacheLauncherTest#testUpdateEnabled_Disabled_ThenEnabled
(UNKNOWN)
C  860.211s Main  [  FAILED  ]
org.chromium.chrome.browser.precache.PrecacheLauncherTest#testUpdateEnabled_SyncNotReady_ThenEnabled
(UNKNOWN)

 Link to bot:

https://uberchromegw.corp.google.com/i/chromium.linux/builders/Android%20Test...


Original issue's description:
> PrecacheFetcher::CancelPrecaching should run in the main UI thread
> 
> Reducing the possibilities of crash in CancelPrecaching.
> 
> BUG=619111
> 
> Committed: https://crrev.com/28e7a0cc33dafc8719c4b9c740d79a47ff90f067
> Cr-Commit-Position: refs/heads/master@{#404792}

TBR=sclittle@chromium.org,rajendrant@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=619111
==========

[commit-bot: I haz the power, 2016-07-12 14:34:41]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-07-12 14:34:51]

CQ bit was unchecked.

[commit-bot: I haz the power, 2016-07-12 14:36:29]

Description was changed from

==========
Revert of PrecacheFetcher::CancelPrecaching should run in the main UI thread
(patchset #4 id:60001 of https://codereview.chromium.org/2137593002/ )

Reason for revert:
Android Test (dbg) has turned red, with failures:
C  860.211s Main  [  FAILED  ]
org.chromium.chrome.browser.precache.PrecacheControllerTest#testDeviceStateChangeCancels
C  860.211s Main  [  FAILED  ]
org.chromium.chrome.browser.precache.PrecacheControllerTest#testTimeoutCancelsPrecaching
C  860.211s Main  [  FAILED  ]
org.chromium.chrome.browser.precache.PrecacheControllerTest#testTimeoutDoesNotCancelIfNotPrecaching
(UNKNOWN)
C  860.211s Main  [  FAILED  ]
org.chromium.chrome.browser.precache.PrecacheLauncherTest#testUpdateEnabled_Disabled_ThenEnabled
(UNKNOWN)
C  860.211s Main  [  FAILED  ]
org.chromium.chrome.browser.precache.PrecacheLauncherTest#testUpdateEnabled_SyncNotReady_ThenEnabled
(UNKNOWN)

 Link to bot:

https://uberchromegw.corp.google.com/i/chromium.linux/builders/Android%20Test...


Original issue's description:
> PrecacheFetcher::CancelPrecaching should run in the main UI thread
> 
> Reducing the possibilities of crash in CancelPrecaching.
> 
> BUG=619111
> 
> Committed: https://crrev.com/28e7a0cc33dafc8719c4b9c740d79a47ff90f067
> Cr-Commit-Position: refs/heads/master@{#404792}

TBR=sclittle@chromium.org,rajendrant@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=619111
==========

to

==========
Revert of PrecacheFetcher::CancelPrecaching should run in the main UI thread
(patchset #4 id:60001 of https://codereview.chromium.org/2137593002/ )

Reason for revert:
Android Test (dbg) has turned red, with failures:
C  860.211s Main  [  FAILED  ]
org.chromium.chrome.browser.precache.PrecacheControllerTest#testDeviceStateChangeCancels
C  860.211s Main  [  FAILED  ]
org.chromium.chrome.browser.precache.PrecacheControllerTest#testTimeoutCancelsPrecaching
C  860.211s Main  [  FAILED  ]
org.chromium.chrome.browser.precache.PrecacheControllerTest#testTimeoutDoesNotCancelIfNotPrecaching
(UNKNOWN)
C  860.211s Main  [  FAILED  ]
org.chromium.chrome.browser.precache.PrecacheLauncherTest#testUpdateEnabled_Disabled_ThenEnabled
(UNKNOWN)
C  860.211s Main  [  FAILED  ]
org.chromium.chrome.browser.precache.PrecacheLauncherTest#testUpdateEnabled_SyncNotReady_ThenEnabled
(UNKNOWN)

 Link to bot:

https://uberchromegw.corp.google.com/i/chromium.linux/builders/Android%20Test...

Original issue's description:
> PrecacheFetcher::CancelPrecaching should run in the main UI thread
>
> Reducing the possibilities of crash in CancelPrecaching.
>
> BUG=619111
>
> Committed: https://crrev.com/28e7a0cc33dafc8719c4b9c740d79a47ff90f067
> Cr-Commit-Position: refs/heads/master@{#404792}

TBR=sclittle@chromium.org,rajendrant@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=619111

Committed: https://crrev.com/285187208715fc68c217d4a7d237f96277fce50c
Cr-Commit-Position: refs/heads/master@{#404810}
==========

[commit-bot: I haz the power, 2016-07-12 14:36:30]

Patchset 1 (id:??) landed as
https://crrev.com/285187208715fc68c217d4a7d237f96277fce50c
Cr-Commit-Position: refs/heads/master@{#404810}