dashboard: revoke no longer working reproducers

Reuse the existing patch testing mechanism to periodically re-check
existing reproducers. If a repro no longer works, mark it as such and
don't consider during bug obsoletion testing.

For obsoleted bugs, pass also a string argument specifying the reason
for the obsoletion. This will make email messages more user-friendly and
also let us later estimate the amount of no longer relevant bugs that we
had on the dashboard.

1 files changed, 11 insertions, 4 deletions

diff --git a/dashboard/dashapi/dashapi.go b/dashboard/dashapi/dashapi.go
index cdefb8080..d5ccc1e0f 100644
--- a/dashboard/dashapi/dashapi.go
+++ b/dashboard/dashapi/dashapi.go
@@ -433,6 +433,7 @@ type BugUpdate struct {
 	ExtID           string
 	Link            string
 	Status          BugStatus
+	StatusReason    BugStatusReason
 	ReproLevel      ReproLevel
 	DupOf           string
 	OnHold          bool     // If set for open bugs, don't upstream this bug.
@@ -608,10 +609,11 @@ func (dash *Dashboard) LoadBug(id string) (*BugReport, error) {
 }
 
 type (
-	BugStatus  int
-	BugNotif   int
-	ReproLevel int
-	ReportType int
+	BugStatus       int
+	BugStatusReason string
+	BugNotif        int
+	ReproLevel      int
+	ReportType      int
 )
 
 const (
@@ -625,6 +627,11 @@ const (
 )
 
 const (
+	InvalidatedByRevokedRepro = BugStatusReason("invalid_no_repro")
+	InvalidatedByNoActivity   = BugStatusReason("invalid_no_activity")
+)
+
+const (
 	// Upstream bug into next reporting.
 	// If the action succeeds, reporting sends BugStatusUpstream update.
 	BugNotifUpstream BugNotif = iota