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

Issue 594207 link

Starred by 1 user
Status: Assigned
Owner:
ihf@chromium.org
Cc:
█ keta...@chromium.org
█ sosa@chromium.org
steve...@chromium.org
achuith@chromium.org
ihf@chromium.org
chromeos-continuous-integration-fire-hose@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Limit chrome image size in compile stage

Project Member Reported by steve...@chromium.org, Mar 11 2016 
Twice in the past three weeks the cros PFQ builders started failing because the chrome image size increased and the size of the chromeos partition containing the chrome image exceeded its limit.

Both times the change was unrelated to chromeos and the developer was likely unaware of this limitation.

We should set a ceiling for the Chrome image size and test against it in the build step so that builders on the Chromium tree (e.g. https://build.chromium.org/p/chromium.chromiumos/builders/ChromiumOS%20x86-generic%20Compile) will fail (with a clear message as to why) when this occurs.

These builders cycle frequently so it will be much easier to track down the change responsible quickly.

Comment 1 by akes...@chromium.org, Mar 11 2016

Owner: steve...@chromium.org
The builder you linked to is not a chromite/cbuildbot based build. ChromeOS infra has no insight or ownership of that side of the build. Sounds like a fine idea, but should be driven from the chrome or chrome infra side.

Comment 2 by steve...@chromium.org, Mar 11 2016

Cc: sosa@chromium.org
Do you have any suggestions as to who on Chrome Infra might be a good owner? Thanks!

Comment 3 by ihf@chromium.org, Mar 11 2016

Owner: ihf@chromium.org
I was going to add a check for this anyways.

Comment 4 by keta...@chromium.org, Mar 11 2016

Labels: Hotlist-CrOS-Gardener

Comment 5 by benhenry@chromium.org, Jul 29 2016

Components: -Build Infra>Client>ChromeOS

Comment 6 by akes...@chromium.org, Jul 17 2017

Labels: akeshet-pending-downgrade
ChromeOS Infra P1 Bugscrub.

P1 Bugs in this component should be important enough to get weekly status updates.

Is this already fixed?  -> Fixed
Is this no longer relevant? -> Archived or WontFix
Is this not a P1, based on go/chromeos-infra-bug-slo rubric? -> lower priority.
Is this a Feature Request rather than a bug? Type -> Feature
Is this missing important information or scope needed to decide how to proceed? -> Ask question on bug, possibly reassign.
Does this bug have the wrong owner? -> reassign.

Bugs that remain in this state next week will be downgraded to P2.

Comment 7 by akes...@chromium.org, Jul 24 2017

Labels: -akeshet-pending-downgrade Pri-2
ChromeOS Infra P1 Bugscrub.

Issue untouched in a week after previous message. Downgrading to P2.

Comment 8 by akes...@chromium.org, Mar 30 2018

Components: Infra>Client>ChromeOS>CI

Comment 9 by akes...@chromium.org, Mar 30 2018

Components: -Infra>Client>ChromeOS
►

Sign in to add a comment