Use drone_installation_dir for all activities on drones, including results dirs and temp dirs.  Previously it would use the drone_installation_dir for executing drone_utility, but would use the scheduler results dir for everything else.

Added a whole bunch of extra unit tests to cover the relevant code paths in drone_manager.

Signed-off-by: Steve Howard <showard@google.com>


git-svn-id: http://test.kernel.org/svn/autotest/trunk@3827 592f7852-d20e-0410-864c-8624ca9c26a4
2 files changed