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?
Comment 1 by vapier@chromium.org
, Jul 21