diff options
| author | Dmitry Vyukov <dvyukov@google.com> | 2019-11-27 14:05:14 +0100 |
|---|---|---|
| committer | Dmitry Vyukov <dvyukov@google.com> | 2019-11-27 14:05:14 +0100 |
| commit | 6f7be11fa1dfb7538af54ffafd1cc644d3975a1d (patch) | |
| tree | 2c5e659127245a15b559ecc1dcda66cacbfbac6c /dashboard/dashapi/dashapi.go | |
| parent | 9f5fd6fe1a3835945ce119f2b5d3633d3b81ff61 (diff) | |
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
Diffstat (limited to 'dashboard/dashapi/dashapi.go')
| -rw-r--r-- | dashboard/dashapi/dashapi.go | 5 |
1 files changed, 3 insertions, 2 deletions
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) { |