Add logspam to help diagnose flaky tests

chrome/browser/extensions/api/automation_internal/automation_util.cc

Index: chrome/browser/extensions/api/automation_internal/automation_util.cc
diff --git a/chrome/browser/extensions/api/automation_internal/automation_util.cc b/chrome/browser/extensions/api/automation_internal/automation_util.cc
index 591a86f4da881b1f157e9f23843340f9e38d2b71..7ecad6aacd93d7de676d4c2e9c9e85eb7be61ed9 100644
--- a/chrome/browser/extensions/api/automation_internal/automation_util.cc
+++ b/chrome/browser/extensions/api/automation_internal/automation_util.cc
@@ -133,7 +133,6 @@ void DispatchAccessibilityEventsToAutomation(
       details.begin();
   for (; iter != details.end(); ++iter) {
     const content::AXEventNotificationDetails& event = *iter;
-
     AXEventParams ax_event_params;
     ax_event_params.process_id = event.process_id;
     ax_event_params.routing_id = event.routing_id;
@@ -149,6 +148,12 @@ void DispatchAccessibilityEventsToAutomation(
       ax_tree_update.nodes.push_back(out_node);
     }
 
+    LOG(INFO) << "AccessibilityEventReceived { "
+              << "process_id: " << event.process_id
+              << ", routing_id:" << event.routing_id
+              << ", event_type:" << ui::ToString(event.event_type)
+              << "}; dispatching to JS";
+
     // TODO(dtseng/aboxhall): Why are we sending only one update at a time? We
     // should match the behavior from renderer -> browser and send a
     // collection of tree updates over (to the extension); see