android 4.4 build failing due to space issue
Bug #1252019 reported by
vishal
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linaro Android |
Fix Released
|
High
|
vishal | ||
Linaro Android Infrastructure |
Invalid
|
High
|
Paul Sokolovsky |
Bug Description
Android 4.4 failed due to space issue:
https:/
Changed in linaro-android-infrastructure: | |
importance: | Undecided → High |
assignee: | nobody → Paul Sokolovsky (pfalcon) |
milestone: | none → 2013.11 |
Changed in linaro-android: | |
status: | New → Confirmed |
importance: | Undecided → Critical |
milestone: | none → 13.11 |
importance: | Critical → High |
Changed in linaro-android: | |
milestone: | 13.11 → 13.12 |
Changed in linaro-android: | |
milestone: | 13.12 → 14.01 |
To post a comment you must log in.
From build log, we have:
mkfs.vfat 3.0.12 (29 Oct 2011) /system- disc/usr/ icu/icudt51l. dat': No space left on device /system- disc/usr/ icu/icudt51l. dat': No space left on device
Loop device does not match a floppy size, using default hd params
Image Name: boot script
Created: Sun Nov 17 15:08:26 2013
Image Type: ARM Linux Script (uncompressed)
Data Size: 434 Bytes = 0.42 kB = 0.00 MB
Load Address: 00000000
Entry Point: 00000000
Contents:
Image 0: 426 Bytes = 0.42 kB = 0.00 MB
mv: writing `/tmp/tmpJA0xpN
mv: failed to extend `/tmp/tmpJA0xpN
That pretty much looks like build creates an FS image, they mounts, then writes to it, and that's when out of space error happens. So, it's not build slave's out of space, but rather target image out of space. So, handing over back to Android people for further investigation.