From 633f9fa5646ebf9353a37cc48cadeb0436b274b8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Kamil=20P=C3=A1ral?= <kparal@redhat.com>
Date: Tue, 12 Mar 2019 16:12:10 +0100
Subject: [PATCH] taskotron: allow CRASHED outcome in ResultsDB

Task developers can then track crashed tests and spot the problems.
See https://pagure.io/task-abicheck/issue/19
---
 roles/taskotron/resultsdb-backend/templates/settings.py.j2 | 2 --
 1 file changed, 2 deletions(-)

diff --git a/roles/taskotron/resultsdb-backend/templates/settings.py.j2 b/roles/taskotron/resultsdb-backend/templates/settings.py.j2
index 765c0185dd..2a9f8da473 100644
--- a/roles/taskotron/resultsdb-backend/templates/settings.py.j2
+++ b/roles/taskotron/resultsdb-backend/templates/settings.py.j2
@@ -16,8 +16,6 @@ MESSAGE_BUS_PUBLISH_TASKOTRON = True
 MESSAGE_BUS_PLUGIN = 'fedmsg'
 MESSAGE_BUS_KWARGS = {'modname': 'resultsdb'}
 
-{% if deployment_type in ['dev']%}
 # Extend the list of allowed outcomes
 # See: https://pagure.io/task-abicheck/issue/19
 ADDITIONAL_RESULT_OUTCOMES = ('CRASHED', )
-{% endif %}