Log - b5ad484fd09bfc39c62e2e34a939176010345149 - platform/external/autotest

8993161 autotest: Drop support for drones without SSP by Prathmesh Prabhu · 6 years ago
036b3a6 [autotest] Merge scheduler/drone_manager by Allen Li · 8 years ago
ec1d47d [autotest] Add support for scheduler to honor require_ssp attribute in control file by Dan Shi · 10 years ago
b9144a4 [autotest] Check server database before services start by Dan Shi · 10 years ago
cf731e3 [autotest] Scheduler, drone_manager, drone_utility stats. by Prashanth B · 10 years ago
36accc6 [autotest] Fixing and re-enabling monitor_db_functional_test. by Jakob Jülich · 10 years ago
340fd1e [autotest] Threaded asynchronous task execution on drones. by Prashanth B · 10 years ago
3ef8213 Revert "[autotest] Threaded asynchronous task execution on drones." by Prashanth B · 10 years ago
0933899 [autotest] Threaded asynchronous task execution on drones. by Prashanth B · 10 years ago
882f15b Autotest: Add logging to copy to results repo logic by Simran Basi · 11 years ago
76fcf19 Add ability to associate drone sets with jobs. This restricts a job to by jamesren · 14 years ago
37b5045 Fixes to drone_manager behavior. by jamesren · 14 years ago
d349624 Fix DroneManager._drop_old_pidfiles() -- use items() instead of iteritems() to avoid concurrent modification exception. Added unit test. by showard · 15 years ago
418785b Some improvements to process tracking in the scheduler. by showard · 15 years ago
9bb960b Support restricting access to drones by user. Administrators can put lines like by showard · 15 years ago
ac5b000 * get rid of the code to create the drone temp dir in drones.py. This used to be necessary because we needed that directory just to run drone_utility (so we could put the pickle file there). But now we use stdin, so we don't need this anymore. (drone_utility still initializes the temp dir for its own use.) by showard · 15 years ago
202343e On the results drone, execute code from the results dir. by showard · 15 years ago
2aafd90 Need to get the drone temporary directory under the results dir as well. Added unit tests to check this and to check the behavior of attach_file_to_execution, which was being affected by this bug (but wasn't actually buggy itself). by showard · 15 years ago
c75fded Fix the drone results dir computation. I forgot that the results don't just go under the drone_installation_directory, they go under "results" in there. by showard · 15 years ago
42d4498 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. by showard · 15 years ago
6631273 Make a bunch of stuff executable by mbligh · 15 years ago
e39ebe9 temporary fix for bug in scheduling when at capacity. if no drone has capacity, pick the one with the least load. by showard · 15 years ago