Autotest: Add logging to copy to results repo logic
We have been only using 1 drone because of the email spam sent out
regarding copying to results repo. We want to try enabling multiple
drones so that the lab will not go down in the case one drone dies.
Copy_to_results_repository is now gated by the enale_archiving flag,
meaning it should not happen.
Added logging to SSHHost's get/send file methods that drone_utility
uses to send files to the results repo. Also added logging to the
drone_utility's send/get functions as well.
BUG=chromium:231452
TEST=Local setup with multiple drones. Ensure tests still run.
Change-Id: I62a0196880d4b25ff8abb47825e280d193a4b9b7
Reviewed-on: https://chromium-review.googlesource.com/175005
Reviewed-by: Simran Basi <sbasi@chromium.org>
Commit-Queue: Simran Basi <sbasi@chromium.org>
Tested-by: Simran Basi <sbasi@chromium.org>
diff --git a/scheduler/drone_manager_unittest.py b/scheduler/drone_manager_unittest.py
index 6d9949d..d2ee2a2 100755
--- a/scheduler/drone_manager_unittest.py
+++ b/scheduler/drone_manager_unittest.py
@@ -5,7 +5,7 @@
from autotest_lib.client.common_lib import global_config
from autotest_lib.client.common_lib.test_utils import mock
from autotest_lib.scheduler import drone_manager, drone_utility, drones
-from autotest_lib.scheduler import scheduler_config
+from autotest_lib.scheduler import scheduler_config, site_drone_manager
class MockDrone(drones._AbstractDrone):
def __init__(self, name, active_processes=0, max_processes=10,
@@ -293,6 +293,7 @@
def test_copy_to_results_repository(self):
+ site_drone_manager.ENABLE_ARCHIVING = True
self.manager.copy_to_results_repository(self.mock_drone_process,
self._SOURCE_PATH)
self.assert_(self.mock_drone.was_file_sent(