Happened again in eve-tot-chrome-pfq-informational
https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8936868882655593152


I wonder whether this is related https://chromium-review.googlesource.com/816022.  The CL made AutotestPrivateLoginStatusFunction async. But chrome.login_status tries to fetch it immediately after the call [1] and could end up getting a null on slow bot.

[1] https://cs.corp.google.com/chromeos_public/src/third_party/autotest/files/client/common_lib/cros/chrome.py?rcl=ad6112ba10c2818a10cac19b78f3cc93c81f615b&l=239

Maybe we could try to pull login status several times instead of immediately return test failure? I will work on a CL to fix.

It looks like this is still failing on M71

https://stainless.corp.google.com/search?test=%5Etelemetry%5C_LoginTest%24&exclude_non_release=true&exclude_cts=true&col=build&row=board_model&view=matrix&first_date=2018-09-07&last_date=2018-09-13

Looks green?

I think this should be fixed by achuith's CL: https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/1236653