From 163f510d99dcf7239e56cef53bbca39db1f2fd9b Mon Sep 17 00:00:00 2001
From: Aleksandr Nogikh <nogikh@google.com>
Date: Fri, 7 Mar 2025 16:05:31 +0100
Subject: dashboard: include revoked reproducers in reports

Context: #5829.

Let's not pretend that the revoked reproducer never existed and still
report it. It will avoid unexpected side-effects for the higher-level
logic.

There may be better ways to resolve the bug, but let's first just get it
fixed to prevent syzbot from spamming the mailing lists.

Add a test to verify the new behavior.
---
 dashboard/dashapi/dashapi.go | 1 +
 1 file changed, 1 insertion(+)

(limited to 'dashboard/dashapi/dashapi.go')

diff --git a/dashboard/dashapi/dashapi.go b/dashboard/dashapi/dashapi.go
index 0d4bee371..317fcb5a2 100644
--- a/dashboard/dashapi/dashapi.go
+++ b/dashboard/dashapi/dashapi.go
@@ -459,6 +459,7 @@ type BugReport struct {
 	ReproCLink        string
 	ReproSyz          []byte
 	ReproSyzLink      string
+	ReproIsRevoked    bool
 	ReproOpts         []byte
 	MachineInfo       []byte
 	MachineInfoLink   string
-- 
cgit mrf-deployment