Disable delaying of Apps installation on Chrome OS for first time sign-in

Disable delaying of Apps installation on Chrome OS for first time sign-in

This behavior is introduced by a772ed62ff0641df984feffe977b1545e94d53f1.
It makes ExternalPrefLoader not being ready when user sign in to Chromebook for
the first time and accidentally blocks all installation of external extensions
if Chrome Sync is turned off, including force installed extensions by policy.

BUG=457539
TEST=manual

Committed: https://crrev.com/9a5194c07bd95febb99e61cdaaf9e42e602bd0be
Cr-Commit-Position: refs/heads/master@{#317074}

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

[binjin, 2015-02-19 14:40:59]

binjin@chromium.org changed reviewers:
+ asargent@chromium.org, nkostylev@chromium.org

[binjin, 2015-02-19 14:44:06]

Nikita, Antony: Could you please have a look at this as reviewers of the
original CL. See https://codereview.chromium.org/650763003

[binjin, 2015-02-19 15:15:47]

binjin@chromium.org changed reviewers:
+ kalman@chromium.org

[binjin, 2015-02-19 15:15:48]

Just realized that Antony is OOO as well.

Benjamin: Could you have a look at this?

[Nikita (slow), 2015-02-19 16:36:56]

lgtm

[not at google - send to devlin, 2015-02-19 17:28:54]

lgtm, revert sounds like the right thing to do - are you planning on revising a
(more complex) version of this?

(because we're also working on lower level ways to throttle extension process
creation)

[binjin, 2015-02-19 17:50:40]

On 2015/02/19 17:28:54, kalman wrote:
> lgtm, revert sounds like the right thing to do - are you planning on revising
a
> (more complex) version of this?
> 
> (because we're also working on lower level ways to throttle extension process
> creation)

I think I will leave Dmitry for the revising work, since I'm not familiar with
the code.

[binjin, 2015-02-19 17:50:54]

The CQ bit was checked by binjin@chromium.org

[commit-bot: I haz the power, 2015-02-19 17:51:44]

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

[commit-bot: I haz the power, 2015-02-19 17:58:12]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-02-19 17:59:28]

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

[Ken Russell (switch to Gerrit), 2015-02-20 01:42:47]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/939183003/ by kbr@chromium.org.

The reason for reverting is: Seems to have broken PDFExtensionTest, blocking
Blink rolls. See crbug.com/460328.
.

[binjin, 2015-02-20 04:42:25]

On 2015/02/20 01:42:47, Ken Russell wrote:
> A revert of this CL (patchset #1 id:1) has been created in
> https://codereview.chromium.org/939183003/ by mailto:kbr@chromium.org.
> 
> The reason for reverting is: Seems to have broken PDFExtensionTest, blocking
> Blink rolls. See crbug.com/460328.
> .

It seems that this is unrelated to the test failures:
1. The tests are still failing, and not only on cros anymore.
2. The failure is directly caused by assertion error in webkit.
3. This CL is not on the blamelist of the first failing build, see
http://build.chromium.org/p/chromium.webkit/builders/Linux%20ChromiumOS%20Tes...

So I gonna reland it.

[binjin, 2015-02-20 04:43:17]

The CQ bit was checked by binjin@chromium.org

[commit-bot: I haz the power, 2015-02-20 04:44:05]

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

[commit-bot: I haz the power, 2015-02-20 04:44:38]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-02-20 04:45:18]

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