From 52a20ba400d467dc0d53ce984fcdb007afd9aea1 Mon Sep 17 00:00:00 2001
From: Dmitry Vyukov <dvyukov@google.com>
Date: Fri, 22 Mar 2019 18:38:28 +0100
Subject: dashboard/app: properly handle build failures

Separate kernel and syzkaller build failures.
Fix logic to understand when a build is fixed:
look if kernel/syzkaller commit changes to understand
if it's a new good build or re-upload of an old build.

Fixes #1014
---
 dashboard/dashapi/dashapi.go | 31 ++++++++++++++++---------------
 1 file changed, 16 insertions(+), 15 deletions(-)

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

diff --git a/dashboard/dashapi/dashapi.go b/dashboard/dashapi/dashapi.go
index 238e1742a..fffc0b8e1 100644
--- a/dashboard/dashapi/dashapi.go
+++ b/dashboard/dashapi/dashapi.go
@@ -54,21 +54,22 @@ func NewCustom(client, addr, key string, ctor RequestCtor, doer RequestDoer,
 
 // Build describes all aspects of a kernel build.
 type Build struct {
-	Manager           string
-	ID                string
-	OS                string
-	Arch              string
-	VMArch            string
-	SyzkallerCommit   string
-	CompilerID        string
-	KernelRepo        string
-	KernelBranch      string
-	KernelCommit      string
-	KernelCommitTitle string
-	KernelCommitDate  time.Time
-	KernelConfig      []byte
-	Commits           []string // see BuilderPoll
-	FixCommits        []Commit
+	Manager             string
+	ID                  string
+	OS                  string
+	Arch                string
+	VMArch              string
+	SyzkallerCommit     string
+	SyzkallerCommitDate time.Time
+	CompilerID          string
+	KernelRepo          string
+	KernelBranch        string
+	KernelCommit        string
+	KernelCommitTitle   string
+	KernelCommitDate    time.Time
+	KernelConfig        []byte
+	Commits             []string // see BuilderPoll
+	FixCommits          []Commit
 }
 
 type Commit struct {
-- 
cgit mrf-deployment