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

Issue 592059 link

Starred by 2 users

Issue metadata

Status: Archived
Owner: ----
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Feature



Sign in to add a comment

send an alert if the number of prebuilt-derived packages drops below threshold

Project Member Reported by akes...@chromium.org, Mar 4 2016

Issue description

As we learned from https://bugs.chromium.org/p/chromium/issues/detail?id=591471 , it is possible for use to stop publishing prebuilts and not notice for a long time.

Add some kind of alert to prevent this from happening again. This may take the form of an alert email from slaves, or a monarch/statsd stat that shows number of packages (for given build config) build from source vs. from prebuilt.
 
Cc: dgarr...@chromium.org jrbarnette@chromium.org
Owner: akes...@chromium.org
@don and richard - ideas on this? 
Not a clear answer, but a thought....

When we preserve a chroot from a previous build, it contains binary prebuilts from the previous build.

If there are prebuilts from the old chroot that are not in GS for ebuilds not uprevved by the current build, then we failed to upload those prebuilts after the previous build.

I'm sure there are some edge cases to be worked out, but this seems like a string enough signal to be worth a warning.

Comment 3 by benhenry@google.com, Apr 26 2016

Components: Infra>Client>ChromeOS
Labels: -Infra-ChromeOS
Owner: chingcodes@chromium.org
Reviving this old bug, might be a good follow-up to the parallel_emerge instrumentation. The alert could conceivable come from monarch, if we build a metric around this properly.
Owner: ----
Status: Archived (was: Untriaged)
This bug is very old, is Untriaged, and has no owner.  If it is still relevant, reopen as Untriaged or open a new bug

Sign in to add a comment