From 4791c8e9d55c8717073396d3f46791ebbd3cf6a5 Mon Sep 17 00:00:00 2001
From: Aleksandr Nogikh <nogikh@google.com>
Date: Mon, 19 Dec 2022 18:22:11 +0100
Subject: dashboard: don't retest revoked reproducers

We are already quite cautious re. the retest results -- the reproducer
is preserved if we have any type of crash/error. It seems to be highly
unlikely that, once the reproducer stopped to cause any crashes at all,
that it will start working again.
---
 dashboard/app/jobs.go | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/dashboard/app/jobs.go b/dashboard/app/jobs.go
index e31b0ae81..d94c08b09 100644
--- a/dashboard/app/jobs.go
+++ b/dashboard/app/jobs.go
@@ -311,6 +311,10 @@ func handleRetestForBug(c context.Context, now time.Time, bug *Bug, bugKey *db.K
 		if now.Sub(crash.LastReproRetest) < config.Obsoleting.ReproRetestPeriod {
 			continue
 		}
+		if crash.ReproIsRevoked {
+			// No sense in retesting the already revoked repro.
+			continue
+		}
 		// TODO: check if the manager can do such jobs.
 		if managerHasJob[crash.Manager] {
 			continue
-- 
cgit mrf-deployment