Friendly ping for status:-)

There are customers directly reaching out because of command timeout: https://bugs.chromium.org/p/chromium/issues/detail?id=582506#c17

And adding this log would help us identify the issue.

I will do this early next week, after finishing the other one.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/10e9c2815e16885596c7a183950d6680d1d33358

commit 10e9c2815e16885596c7a183950d6680d1d33358
Author: hunyadym <hunyadym@chromium.org>
Date: Thu Jun 30 12:51:34 2016

Add logging of remote command invalidations.

BUG= 619741 

Review-Url: https://codereview.chromium.org/2108873004
Cr-Commit-Position: refs/heads/master@{#403157}

[modify] https://crrev.com/10e9c2815e16885596c7a183950d6680d1d33358/chrome/browser/policy/cloud/remote_commands_invalidator.cc
[modify] https://crrev.com/10e9c2815e16885596c7a183950d6680d1d33358/components/policy/core/common/remote_commands/remote_commands_service.cc

Could we now remove this logging spam, given that the referenced issues are long resolved?

Did we actually resolve those issues?

Re comment 9: Maybe I'm out of the context, but the referenced bug 582506 has no reports in the last 6 months, and the last said that something works for them.
If I'm wrong and the issue is still under investigation, then please ignore my comments here.

I think it mostly just fell off the radar, rather than being fixed. Most likely ivan will look at remote command reliability once he's done with remote audio controls, so let's keep these in place until we feel confident that issue is resolved.