Current status:

Seeing "Error: chrome://policy shows the incorrect value for ProxySettings! Expected None, got ." errors on coral devices

Timeouts are somewhat regular but also not as bad as originally mentioned in this bug.

Maybe this will be fixed by  crbug.com/809222 ?

This is a problem with this particular autotest - there's an unhandled timeout that pops up sometimes.  Unrelated to  issue 809222 .

Katherine, do these timeouts still happen? 90s sounds like a long time, maybe chrome hangs for some reason.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/autotest/+/d4b309b56f0958bf9460c002b887c23a19a2569a

commit d4b309b56f0958bf9460c002b887c23a19a2569a
Author: Katherine Threlkeld <kathrelkeld@google.com>
Date: Fri Mar 02 00:13:24 2018

[Autotest] Add retry to url navigation in policy_Proxy test

Test occasionally fails in the lab with an uncaught timeout.
Add a retry and, if that fails, catch the error.  I reproed
the timeout at my desk, but was unable to rerpo the catch
as test passed every time.

Also fixed some docstring formatting, removed some comments,
and changed the url under test.

TEST=ran the failing test ~500 times; ran all control files
BUG=chromium:779700

Change-Id: Ie32a245009033fa88892784fb3d8cea8539244cd
Reviewed-on: https://chromium-review.googlesource.com/935083
Commit-Ready: Katherine Threlkeld <kathrelkeld@chromium.org>
Tested-by: Katherine Threlkeld <kathrelkeld@chromium.org>
Reviewed-by: Kevin Shelton <kmshelton@chromium.org>

[modify] https://crrev.com/d4b309b56f0958bf9460c002b887c23a19a2569a/client/cros/enterprise/enterprise_policy_base.py
[modify] https://crrev.com/d4b309b56f0958bf9460c002b887c23a19a2569a/client/site_tests/policy_ProxySettings/policy_ProxySettings.py