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

Issue 663060 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 709214
Owner: ----
Closed: Apr 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug



Sign in to add a comment

Every continuous chromium builder should have a matching tryserver (potentially optional)

Project Member Reported by dpranke@chromium.org, Nov 7 2016

Issue description

It is very annoying to have continuous builders that do not have matching tryservers; when we don't have a matching tryserver, it means that reproducing build failures is much harder.

Generally speaking we want every builder to have a matching tryserver in the commit queue. However, some configurations are too slow (or too resource intensive) to put into the CQ and still keep reasonable CQ performance. For those configs, though, we should still have matching *optional* trybots.

We do have many optional trybots, but I'm filing this bug to track getting matching optional trybots for the remaining configs and then adding some sort of presubmit check or test to make sure we enforce this.
 
Summary: Every continuous chromium builder should have a matching tryserver (potentially optional) (was: Every continuous chromium builder should have a matching tryserve (potentially optional))
Cc: -andyb...@chromium.org
Owner: andyb...@chromium.org
Status: Assigned (was: Available)
Owner: ----
Status: Available (was: Assigned)
I'm guessing this shouldn't actually be andybons@ any more :).

@phajdan.jr, you might want to own this.
Mergedinto: 709214
Status: Duplicate (was: Available)
I'm going to dup this into crbug.com/709214, where there is more info on how we enforce this (which we already do) and the list of missing builders.

Sign in to add a comment