New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 901158 link

Starred by 1 user
Status: Available
Owner: ----
Cc:
mastiz@chromium.org
dpranke@chromium.org
jbudorick@chromium.org
█ robert...@chromium.org
chanli@chromium.org
lijeffrey@chromium.org
liaoyuke@chromium.org
st...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: ----



Sign in to add a comment

Handle purple builds due to "retry with patch"

Project Member Reported by st...@chromium.org, Nov 1 
https://ci.chromium.org/p/chromium/builders/luci.chromium.try/android-marshmallow-arm64-rel/117037

This is a purpole build due to "retry with patch".
Before, this would be a red build instead.

Comment 1 by erikc...@chromium.org, Nov 1

Cc: dpranke@chromium.org jbudorick@chromium.org
+ dpranke, jbudorick

Can you clarify what the next steps here are?

What can we do to reduce the chance that future recipe changes will break FindIt? Can the implicit dependencies of FindIt on recipes be expressed as assertions in recipe-layer tests?

Comment 2 by dpranke@chromium.org, Nov 1 

I don't understand. This build has steps that are failing due to timeouts and missing shards. It seems like purple is correct, and "retry with patch" has nothing to do with it?

I do agree that we need to understand what FindIt's dependencies on recipes are better, but I'm not seeing the connection in this example.

Comment 3 by jbudorick@chromium.org, Nov 1 

that just looks like the CL under test is horribly broken...

Comment 4 by mastiz@chromium.org, Nov 5

Cc: mastiz@chromium.org
►

Sign in to add a comment