From: Ian Jackson <ian.jackson@eu.citrix.com>
Date: Thu, 25 May 2017 11:47:55 +0000 (+0100)
Subject: ts-hosts-allocate-Executive: Make build failures not be host-sticky
X-Git-Tag: openstack-v11~33
X-Git-Url: http://xenbits.xensource.com/gitweb?a=commitdiff_plain;h=eda155af1dfcd3d7ca67d549edadb5e5953c2259;p=people%2Faperard%2Fosstest.git

ts-hosts-allocate-Executive: Make build failures not be host-sticky

Builds (jobs whose recipe contains `build') are not supposed to
contain host-specific tests.  We already don't care about varying
which host they run on, to hunt for host-specific bugs.

We should also not make build failures sticky to the host they last
failed on.

Fix this by defaulting $prevfail_bonus to 0 in that case, before the
week-long later default is applied.  This means that a build job
runvar would override the built-in default whether that's 7 days or 0.

Reported-by: Roger Pau Monné <roger.pau@citrix.com>
Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com>
---

diff --git a/ts-hosts-allocate-Executive b/ts-hosts-allocate-Executive
index 82ef6285..54366a33 100755
--- a/ts-hosts-allocate-Executive
+++ b/ts-hosts-allocate-Executive
@@ -624,6 +624,7 @@ sub hid_recurse ($$) {
     if ($jobinfo->{recipe} =~ m/build/) {
         $variation_age= 0;
 	$duration_for_cost= $duration + $duration_rightaway_adjust;
+	$prevfail_bonus //= 0;
     }
 
     my $log_variation_age = log(1+$variation_age/86400);