From fb343ecc19084bf98da750539377d508c9e077b3 Mon Sep 17 00:00:00 2001 From: Aleksandr Nogikh Date: Mon, 29 Jan 2024 15:52:06 +0100 Subject: all: record diverted bug reproductions In some cases, we derail during bug reproduction and end up finding and reporting a reproducer for another issue. It causes no problems since it's bucketed using the new title, but it's difficult to trace such situations - on the original bug page, there are no failed reproduction logs and on the new bug page it looks as if we intended to find a reproducer for the bug with the new title. Let's record bug reproduction logs in this case, so that we'd also see a failed bug reproduction attempt on the original bug page. --- dashboard/dashapi/dashapi.go | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) (limited to 'dashboard/dashapi') diff --git a/dashboard/dashapi/dashapi.go b/dashboard/dashapi/dashapi.go index ed9152e09..37aebc631 100644 --- a/dashboard/dashapi/dashapi.go +++ b/dashboard/dashapi/dashapi.go @@ -323,9 +323,11 @@ type Crash struct { Assets []NewAsset GuiltyFiles []string // The following is optional and is filled only after repro. - ReproOpts []byte - ReproSyz []byte - ReproC []byte + ReproOpts []byte + ReproSyz []byte + ReproC []byte + ReproLog []byte + OriginalTitle string // Title before we began bug reproduction. } type ReportCrashResp struct { -- cgit mrf-deployment