ChromeOS: Correctly handle settings.resolve_device_timezone_by_geolocation.

ChromeOS: Correctly handle settings.resolve_device_timezone_by_geolocation.

This CL fixes a problem when checking for if timezone autodetection should
startfor signin screen, when unset preference was treated as "false".

BUG=622555
Review-Url: https://codereview.chromium.org/2855433002
Cr-Commit-Position: refs/heads/master@{#468491}
Committed: https://chromium.googlesource.com/chromium/src/+/ad7d3bec4dd219a4675fcb5473186e96039c2b0a

[Alexander Alekseev, 2017-04-29 02:10:23]

alemate@chromium.org changed reviewers:
+ achuith@chromium.org

[Alexander Alekseev, 2017-04-29 02:10:23]

Please review.

[Alexander Alekseev, 2017-04-29 02:10:30]

The CQ bit was checked by alemate@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-04-29 02:10:49]

Dry run: 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, 2017-04-29 02:33:34]

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

[commit-bot: I haz the power, 2017-04-29 02:33:35]

Dry run: Try jobs failed on following builders:
  linux_chromium_chromeos_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[Alexander Alekseev, 2017-04-29 02:42:05]

The CQ bit was checked by alemate@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-04-29 02:42:28]

Dry run: 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, 2017-04-29 03:08:43]

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

[commit-bot: I haz the power, 2017-04-29 03:08:43]

Dry run: This issue passed the CQ dry run.

[achuithb, 2017-05-01 23:01:56]

So for start screen, the preference was not set?

Is this a regression or has this always been broken?

lgtm regardless.

[Alexander Alekseev, 2017-05-01 23:10:37]

On 2017/05/01 23:01:56, achuithb wrote:
> So for start screen, the preference was not set?
> 
> Is this a regression or has this always been broken?
> 
> lgtm regardless.

It has always been broken.

[Alexander Alekseev, 2017-05-01 23:10:42]

The CQ bit was checked by alemate@chromium.org

[commit-bot: I haz the power, 2017-05-01 23:11:58]

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, 2017-05-01 23:47:11]

CQ is committing da patch.

Bot data: {"patchset_id": 20001, "attempt_start_ts": 1493680242898440,
"parent_rev": "b77b74c5af851a15366fc05ca4fabbf8723334af", "commit_rev":
"ad7d3bec4dd219a4675fcb5473186e96039c2b0a"}

[commit-bot: I haz the power, 2017-05-01 23:47:20]

Description was changed from

==========
ChromeOS: Correctly handle settings.resolve_device_timezone_by_geolocation.

This CL fixes a problem when checking for if timezone autodetection should
startfor signin screen, when unset preference was treated as "false".

BUG=622555
==========

to

==========
ChromeOS: Correctly handle settings.resolve_device_timezone_by_geolocation.

This CL fixes a problem when checking for if timezone autodetection should
startfor signin screen, when unset preference was treated as "false".

BUG=622555

Review-Url: https://codereview.chromium.org/2855433002
Cr-Commit-Position: refs/heads/master@{#468491}
Committed:
https://chromium.googlesource.com/chromium/src/+/ad7d3bec4dd219a4675fcb547318...
==========

[commit-bot: I haz the power, 2017-05-01 23:47:21]

Committed patchset #2 (id:20001) as
https://chromium.googlesource.com/chromium/src/+/ad7d3bec4dd219a4675fcb547318...