New issue
Advanced search Search tips

Issue 866253 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 863077
Owner:
Closed: Jul 21
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Feature



Sign in to add a comment

Exonerate kernel CLs from failures on boards using a different kernel

Project Member Reported by djkurtz@google.com, Jul 21

Issue description

The following is an example CL for the chromeos-4.14 kernel:

https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/1130448/4

A Comment says:
The following build(s) failed:

coral-paladin: The HWTest [bvt-inline] [astronaut] stage failed: ** HWTest failed (code 1) ** in https://luci-milo.appspot.com/buildbot/chromeos/coral-paladin/3871

Your change may have caused this failure. There are also other changes that may be at fault: 69 other changes. See the blamelist for more details.

=================

However, there is no way that this CL caused this failure, since coral-paladin [astronaut] uses a chromeos-4.4 kernel, and this patch was to the chromeos-4.14 kernel.

There is an "Exonerator" in place that should allow board-specific CLs to be submitted despite failures in the same run for unrelated boards.  Can we extend this functionality to include kernel patches being exonerated for failures devices that use a different kernel? 
 
i don't think we need the Exonerator in this case ... there's logic in cbuildbot to detect whether CLs are relevant at the end of a CQ run and merge ones that aren't, so i think this is a scenario where we could merge all the kernel CLs immediately since they aren't used on the boards that failed.

i'm not familiar with that logic though, so don't know where to look ...
Mergedinto: 863077
Status: Duplicate (was: Assigned)
There's a problem with the OS package dev-util/turbostat that's causing this to happen.

Sign in to add a comment