From a7c5aa3fa68531183d71c044b34fcfa513e2f798 Mon Sep 17 00:00:00 2001
From: Clark Boylan <clark.boylan@gmail.com>
Date: Tue, 8 Jan 2013 17:19:10 -0800
Subject: [PATCH] Treat LOST jobs as failures in didAnyJobFail().

Zuul already treats LOST jobs as failures in much of the code. Do the
same in didAnyJobFail so that changes behind a change with a LOST job
get their jobs cancelled.

Change-Id: I1eb819a6cfb3b3ee0a2c131417b00dab1d83f29d
Reviewed-on: https://review.openstack.org/19270
Reviewed-by: James E. Blair <corvus@inaugust.com>
Approved: James E. Blair <corvus@inaugust.com>
Tested-by: Jenkins
---
 zuul/model.py | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/zuul/model.py b/zuul/model.py
index 1cb96f8653..a7c7f0d785 100644
--- a/zuul/model.py
+++ b/zuul/model.py
@@ -120,7 +120,8 @@ class Pipeline(object):
             if not job.voting:
                 continue
             build = changeish.current_build_set.getBuild(job.name)
-            if build and build.result == 'FAILURE':
+            # Treat LOST jobs as failures
+            if build and (build.result == 'FAILURE' or build.result == 'LOST'):
                 return True
         return False