android 4.4 build failing due to space issue

Bug #1252019 reported by vishal
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Linaro Android
Fix Released
High
vishal
Linaro Android Infrastructure
Invalid
High
Paul Sokolovsky
Changed in linaro-android-infrastructure:
importance: Undecided → High
assignee: nobody → Paul Sokolovsky (pfalcon)
milestone: none → 2013.11
Revision history for this message
Paul Sokolovsky (pfalcon) wrote :

From build log, we have:

mkfs.vfat 3.0.12 (29 Oct 2011)
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/system-disc/usr/icu/icudt51l.dat': No space left on device
mv: failed to extend `/tmp/tmpJA0xpN/system-disc/usr/icu/icudt51l.dat': No space left on device

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.

Changed in linaro-android:
assignee: nobody → vishal (vishalbhoj)
Changed in linaro-android-infrastructure:
status: New → Invalid
vishal (vishalbhoj)
Changed in linaro-android:
status: New → Confirmed
importance: Undecided → Critical
milestone: none → 13.11
importance: Critical → High
Fathi Boudra (fboudra)
Changed in linaro-android:
milestone: 13.11 → 13.12
Fathi Boudra (fboudra)
Changed in linaro-android:
milestone: 13.12 → 14.01
Revision history for this message
Fathi Boudra (fboudra) wrote :

Vishal, could you update the status of this bug?

Changed in linaro-android:
milestone: 14.01 → 14.03
Revision history for this message
vishal (vishalbhoj) wrote :

This bug has been fixed.

Changed in linaro-android:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.