autotest: add logging for missing drone metric
Will probably be noisy.
TEST=None
BUG=chromium:853861
Change-Id: I5c7934c94249be6cc10f297ed5afce73b85da699
Reviewed-on: https://chromium-review.googlesource.com/1129365
Commit-Ready: Jacob Kopczynski <jkop@chromium.org>
Tested-by: Jacob Kopczynski <jkop@chromium.org>
Reviewed-by: Prathmesh Prabhu <pprabhu@chromium.org>
diff --git a/scheduler/drone_task_queue.py b/scheduler/drone_task_queue.py
index c506ad0..8e63cc0 100644
--- a/scheduler/drone_task_queue.py
+++ b/scheduler/drone_task_queue.py
@@ -54,6 +54,8 @@
'through get_results.' % self.results)
for drone in drones:
if not drone.get_calls():
+ logging.debug("Drone %s has no work, skipping. crbug.com/853861"
+ , drone)
continue
metric_fields = {
'drone_hostname': drone.hostname,
@@ -62,6 +64,7 @@
drone_reachable = True
try:
drone_results = drone.execute_queued_calls()
+ logging.debug("Drone %s scheduled. crbug.com/853861", drone)
except IOError:
drone_reachable = False
logging.error(