Bisection: Do not try to inhibit queue

In an effort to try to increase the chance that the next bisection
step will get the same host quickly, the cri-bisect uses
mg-queue-inhibit to inhibit all resource allocation for 5 minutes.

With the increasing size of the test facility and the increasing
number of bisector instances running, this is starting to become a
very crude hammer indeed.

And this is largely ineffective anyway as we try bisections every 15
minutes but only inhibit for 5 minutes.

Disable it, until we have a better answer.

Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com>

diff --git a/cri-bisect b/cri-bisect
index 6a2f616e28d52afe555dea0418564c2db3070556..28a8659a3cad7323bfcde7e187591ff422a23290 100644 (file)
--- a/cri-bisect
+++ b/cri-bisect
@@ -66,16 +66,10 @@ perhaps_bisect_step_core () {
 
         perhaps_bisect_step_core_testing_callback
 
-        if test -e $anyflagfile; then
-                inhibitqueue=0
-        else
-                inhibitqueue=300
-        fi
-        
         execute_flight $flight $2
         flight_executed=true
 
-       ./mg-queue-inhibit $inhibitqueue "bisected $branch $flight" ||:
+       # ./mg-queue-inhibit $inhibitqueue "bisected $branch $flight" ||:
 
         compute_state_callback
         send_bisection_email "$flight: tested" -bisectrun