From 6f7be11fa1dfb7538af54ffafd1cc644d3975a1d Mon Sep 17 00:00:00 2001 From: Dmitry Vyukov Date: Wed, 27 Nov 2019 14:05:14 +0100 Subject: dashboard/app: don't report bisections pointing to release commits They should have been detected by "same binary" logic. But the problem is that we may use different compilers for different commits and they switch exactly at release commits. So we can build the release with a differnet compiler than the rest of commits and then obviously it won't be "same binary". Detect release commits separately. Update #1271 --- dashboard/dashapi/dashapi.go | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'dashboard/dashapi') diff --git a/dashboard/dashapi/dashapi.go b/dashboard/dashapi/dashapi.go index b05f3fbf5..833dd099f 100644 --- a/dashboard/dashapi/dashapi.go +++ b/dashboard/dashapi/dashapi.go @@ -172,8 +172,9 @@ const ( type JobDoneFlags int64 const ( - BisectResultMerge JobDoneFlags = 1 << iota // bisected to a merge commit - BisectResultNoop // commit does not affect resulting kernel binary + BisectResultMerge JobDoneFlags = 1 << iota // bisected to a merge commit + BisectResultNoop // commit does not affect resulting kernel binary + BisectResultRelease // commit is a kernel release ) func (dash *Dashboard) JobPoll(req *JobPollReq) (*JobPollResp, error) { -- cgit mrf-deployment