2610 2012-06-14 17:08:05 +0000 poky-tiny builds should be marked as failed if the image size is above a specified threshold 2014-07-11 09:52:54 +0000 1 1 5 Infrastructure AutoBuilder autobuilder unspecified x86 Multiple RESOLVED FIXED https://bugzilla.yoctoproject.org/show_bug.cgi?id=6396 Medium enhancement 1.7 M2 1 dvhart liezhi.yang elizabeth.flanagan infras.ab.watcher Infras.watcher liezhi.yang Martin.Jansa richard.purdie sgw song.liu --- --- Yes (doc changes required) oldest_to_newest 22209 0 dvhart 2012-06-14 17:08:05 +0000 The goal of poky-tiny is to build small images. Sometimes unrelated changes result in packages being pulled into the dependency chain of poky-tiny builds. A QA test comparing the size of a poky-tiny core-image-minimal image to a threshold and marking the build as failed if it exceeds it would make this apparent earlier. TODO: get the threshold 38056 1 sgw 2013-10-18 16:16:35 +0000 Could be sanity test related, so giving it to paul to look into 39413 2 bluelightning 2013-12-16 11:41:44 +0000 This is something that needs to be checked at do_rootfs time; we can't know how large the image will be until that point. A couple of questions: 1) Are we checking the maximum size of the output image file (in which case it is specific to the format type)? Although this is more complicated it does seem like the most sensible given that this is what you'll end up writing to storage on the target. 2) What size threshold do we want to set by default for poky-tiny? 39915 3 bluelightning 2014-01-17 18:11:23 +0000 Setting to NEEDINFO as per above. 40937 4 dvhart 2014-03-06 18:04:47 +0000 How about a SANITY test that does a du -s for tmp/work/core-image-minimal/1.0-r0/rootfs ? That avoids all the fs / package (tar, cpio, etc.) overhead. We should also check the kernel as that is a critical part of this, possibly with two unique THRESHOLD values, maybe: TINY_ROOTFS_THRESHOLD TINY_KERNEL_THRESHOLD Threshold is tricky. Ideally it would be per-machine - but for now, even something like 4MB would be a good starting point. The THRESHOLD should be the easiest aspect of this to change... it should be a variable that a machine config can override as well. For the kernel, 2MB would be a good start I think. THis is assuming eglibc of course, with uclibc, the THRESHOLD for ROOTFS should be more like 2MB. Each could be defined in poky-tiny.conf I suspect, depending on the value of TCLIBC... 43102 5 richard.purdie 2014-05-03 18:04:46 +0000 We already have a setting for the kernel size check. We discussed this at OEDAM and there was general interest in some kind of image size check too as others have run into this kind of issue. A generic image size check would therefore be useful. 43103 6 Martin.Jansa 2014-05-03 18:05:50 +0000 There is meta/lib/oe/image.py _get_rootfs_size function, so it should be enhanced a bit to issue warning when the rootfs exceeds the maximal size. 43789 7 bluelightning 2014-06-05 14:47:35 +0000 *** Bug 6396 has been marked as a duplicate of this bug. *** 44450 8 liezhi.yang 2014-07-11 09:52:54 +0000 Merged into master: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=1cb9f7b00b5ede62a9546c39d798c876775b08c0 http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=7e6eeeefdd0a92df5203d54a9b574957ed2a25ce