grunt missing prebuilts after build flags changed |
|||
Issue descriptionhttps://crrev.com/c/1226276 changed grunt's build flags, and now CQ builds are failing due to missing prebuilts. For example: https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8926710590198574480 https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8926699909642757520
,
Dec 19
,
Dec 19
Grunt is marked experimental in Tree Status.
,
Dec 19
The postsubmit builder for grunt has passed several times since the problematic CL landed, so fresh prebuilts should be available. Our belief is that this is about locally cached prebuilts, which are not preserved on most builders the way they are in the CQ. I've just reinstanced the grunt paladin builder, to clear that state. If the understanding is correct, grunt will build next CQ run, and this can be considered fixed.
,
Dec 20
grunt-paladin is all green aside from two HWTest flakes, grunt-pre-cq and grunt-no-vmtest-pre-cq are both green aside from a few legitimate failures catching bad CLs. Marking this as Fixed.
,
Dec 20
I removed the EXPERIMENTAL status from grunt. |
|||
►
Sign in to add a comment |
|||
Comment 1 by dgarr...@chromium.org
, Dec 19