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

Issue 916366 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit 20 days ago
Closed: Dec 21
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

amd64-generic-full and daisy-full builders are grouped with 'other' in Legoland

Project Member Reported by steve...@chromium.org, Dec 19

Issue description

The amd64-generic-full and daisy-full builders generate the SDK used by the Simple Chrome builders on the chromium waterfall. When they fail, the chromeos SDK used by Simple Chrome can not be updated. This means that the toolchain is not updated and chrome changes dependent on libraries or GN configurations may be blocked.

These builders are currently part of the 'Other' Builders section in Legoland. Because they are lumped with 'Other', it is easy for sheriffs to miss failures, contributing to delays in identifying problems, e.g. issue 913317.

I would propose either putting them in a section under 'Release', or a separate entry below 'Release', since these are the public equivalent.

 
Owner: dburger@chromium.org
David, this is entirely in Legoland.
Separate entry "Full" pointing at:

https://cros-goldeneye.corp.google.com/chromeos/legoland/builderSummary?builderGroups=full&limit=3&buildBranch=master

would be sufficient?

If yes should I remove that subset from "Other"?
I'd like to move everything out of Other to top level. I believe there is an existing bug or two for this from other people as well.
A separate entry for 'Full' would be fine, but it's not very descriptive. Maybe 'Chromiumos'? Or 'Public'?

Status: Fixed (was: Untriaged)
I went with 'Full' as all other sidebar links have the same strong correlation between the link text and the literal builderGroups that are linked to.

Sign in to add a comment