Add an extra delay for policy invalidations to be available.

Add an extra delay for policy invalidations to be available.

The cloud policy refresh scheduler no longer waits for policy invalidations to become available before issuing the first policy fetch. We want to ensure that any policy change that results from this initial policy fetch is counted as a change without invalidations enabled for metrics purposes.

Currently we determine if invalidations are enabled based on whether the invalidation service has reported that it is on. However, there may be a delay between the invalidation service being enabled and the invalidation service actually delivering a pending invalidation. Additionally, on Android the invalidation service always reports that it is enabled. To account for this, add a "grace period" after the invalidation service is enabled during which we still consider invalidations disabled for metrics reporting.

BUG=355884
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=261506

[Steve Condie, 2014-04-02 00:36:15]

CL 2 of 3 for crbug.com/355884

[Joao da Silva, 2014-04-02 07:16:01]

lgtm after fixing the comment

https://codereview.chromium.org/213743014/diff/1/chrome/browser/policy/cloud/...
File chrome/browser/policy/cloud/cloud_policy_invalidator.h (right):

https://codereview.chromium.org/213743014/diff/1/chrome/browser/policy/cloud/...
chrome/browser/policy/cloud/cloud_policy_invalidator.h:60: base::Clock* clock);
Pass this in a scoped_ptr to make the ownership semantics explicit

[Steve Condie, 2014-04-02 18:48:15]

https://codereview.chromium.org/213743014/diff/1/chrome/browser/policy/cloud/...
File chrome/browser/policy/cloud/cloud_policy_invalidator.h (right):

https://codereview.chromium.org/213743014/diff/1/chrome/browser/policy/cloud/...
chrome/browser/policy/cloud/cloud_policy_invalidator.h:60: base::Clock* clock);
On 2014/04/02 07:16:01, Joao da Silva wrote:
> Pass this in a scoped_ptr to make the ownership semantics explicit

Done.

[Steve Condie, 2014-04-02 18:50:24]

The CQ bit was checked by stepco@chromium.org

[commit-bot: I haz the power, 2014-04-02 18:50:44]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/stepco@chromium.org/213743014/20001

[commit-bot: I haz the power, 2014-04-03 08:32:38]

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

[commit-bot: I haz the power, 2014-04-03 08:32:38]

Commit queue rejected this change because the description was changed
between the time the change entered the commit queue and the time it
was ready to commit. You can safely check the commit box again.

[Steve Condie, 2014-04-03 17:52:44]

The CQ bit was checked by stepco@chromium.org

[commit-bot: I haz the power, 2014-04-03 17:53:05]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/stepco@chromium.org/213743014/20001

[commit-bot: I haz the power, 2014-04-03 19:38:51]

Change committed as 261506