Felix Edel 38776452bb Don't use the AnsibleJob in the nodepool client ... This change follows up on a few TODOs left by the lock/unlock nodes on executor change. When locking the nodes on the executor we used the AnsibleJob as a replacement for the old build parameter that was provided to the nodepool client methods as they were originally called by the scheduler. However, the AnsibleJob class should only be used internally by the executor, so we now provide all parameters directly to the nodepool methods. This also annotates the logger in the updated nodepool client methods and fixes an outdated method signature in test_scheduler.TestSemaphore.test_semaphore_zk_error. Remove two comments about storing timestamps on the build request in ZooKeeper as this doesn't make much sense. It sounded like a good idea in the beginning, but with the current solution, the scheduler doesn't need to care about the build request anymore after it was submitted (except for canceling/cleanup purposes) and the result data is self-contained. Change-Id: I2d1005f69904c6ace8f79523133f382af0024c52		2021-09-10 10:55:01 -07:00
..
__init__.py	Add nodepool integration test	2017-01-24 13:37:21 -08:00
test_nodepool_integration.py	Don't use the AnsibleJob in the nodepool client	2021-09-10 10:55:01 -07:00