Determine whether to disable session invalidations at startup

Determine whether to disable session invalidations at startup

BUG=477054
TEST=InvalidationControllerTest.*

Committed: https://crrev.com/4469d4469c152c36f632a6e969b3088e1271340c
Cr-Commit-Position: refs/heads/master@{#341761}

[pkotwicz, 2015-08-04 18:07:02]

Patchset #1 (id:1) has been deleted

[pkotwicz, 2015-08-04 18:14:18]

pkotwicz@chromium.org changed reviewers:
+ nyquist@chromium.org

[pkotwicz, 2015-08-04 18:14:19]

Tommy can you please take a look? This CL is a subset of
https://codereview.chromium.org/1263773007/ with the goal of addressing all of
the conflicts with https://codereview.chromium.org/1247853007/ in a short CL

This CL checks the experiments on init as zea@ has suggested. My understanding
is that field trials are only set when Chrome is restarted though the variations
seed is requested every 5 hours. If the field trials change while Chrome is
running then there is a bug because when the field trial changes we do not
register/unregister for session invalidations

[nyquist, 2015-08-04 19:16:03]

that was nice of you! thanks! lgtm

[pkotwicz, 2015-08-04 19:17:40]

The CQ bit was checked by pkotwicz@chromium.org

[commit-bot: I haz the power, 2015-08-04 19:18:28]

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

[commit-bot: I haz the power, 2015-08-04 19:35:11]

Committed patchset #1 (id:20001)

[commit-bot: I haz the power, 2015-08-04 19:36:47]

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