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

Issue 657045 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Oct 2016
Cc:
█ dshi@chromium.org
briannorris@chromium.org
█ jrbarnette@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

"no space left on device" for cyan-paladin build 670

Project Member Reported by semenzato@chromium.org, Oct 18 2016 
During build_image.  Does it go away by itself or does it need help?  Thanks!

https://uberchromegw.corp.google.com/i/chromeos/builders/cyan-paladin/builds/670/steps/BuildImage/logs/stdio

Comment 1 by jrbarnette@chromium.org, Oct 18 2016 

Most commonly, symptoms like this during build_image means
that the file system in the target image has filled up, meaning
somewhere, the software has gotten bigger than the build is
configured to allow.

If that's so, it's caused by a change in the product, and it's
not an infrastructure bug.  Since the problem occurred in a paladin
run, it may not be a product bug in the tree, but rather was caused
by a change in the CQ run.  If so, it's not even a bug...

Comment 2 by semenzato@chromium.org, Oct 18 2016

Components: -Infra>Client>ChromeOS
Status: WontFix (was: Untriaged)
Thank you Richard.  I should have looked more carefully, I thought we ran out of space on the builder.
►

Sign in to add a comment