<div dir="ltr">This is causing the qemu boot wic test to fail in oe-selftest:<br><br>2018-02-05 15:08:41,786 - oe-selftest - INFO - FAIL [64.639s]: test_qemu (wic.Wic)<br>2018-02-05 15:08:41,786 - oe-selftest - INFO - ----------------------------------------------------------------------<br>2018-02-05 15:08:41,786 - oe-selftest - INFO - Traceback (most recent call last):<br> File "/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-oe-selftest/build/meta/lib/oeqa/core/decorator/__init__.py", line 32, in wrapped_f<br> return func(*args, **kwargs)<br> File "/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-oe-selftest/build/meta/lib/oeqa/selftest/cases/wic.py", line 58, in wrapped_f<br> return func(*args, **kwargs)<br> File "/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-oe-selftest/build/meta/lib/oeqa/selftest/cases/wic.py", line 637, in test_qemu<br> self.assertEqual(output, '/dev/root /\r\n/dev/sda1 /boot\r\n/dev/sda3 /mnt')<br>AssertionError: '/dev/root /\r\n/dev/sda1 /boot\r\n/dev/sda3 /media\r\n/dev/sda4 /mnt' != '/dev/root /\r\n/dev/sda1 /boot\r\n/dev/sda3 /mnt'<br> /dev/root /<br> /dev/sda1 /boot<br>- /dev/sda3 /media<br>- /dev/sda4 /mnt? ^<br>+ /dev/sda3 /mnt? ^<br><br>Presumably this is the initramfs mounting more stuff automatically? I don't have an opinion right now as to whether this is a problem with the initramfs or the test case being too strict...<div><br></div><div>Ross<br><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 1 February 2018 at 14:03, Burton, Ross <span dir="ltr"><<a href="mailto:ross.burton@intel.com" target="_blank">ross.burton@intel.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Sorry, missed this. I'll pull it into MUT and throw it at the autobuilder...<span class="HOEnZb"><font color="#888888"><div><br></div><div>Ross</div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On 31 January 2018 at 22:53, Cal Sullivan <span dir="ltr"><<a href="mailto:california.l.sullivan@intel.com" target="_blank">california.l.sullivan@intel.<wbr>com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Ping.<br>
<br>
---<br>
Cal<div class="m_-9033303757896667203HOEnZb"><div class="m_-9033303757896667203h5"><br>
<br>
On 01/09/2018 05:00 PM, Cal Sullivan wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Anything wrong with this? Haven't seen it hit any mut branches.<br>
<br>
Thanks,<br>
Cal<br>
<br>
On 12/19/2017 02:12 PM, California Sullivan wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
initramfs-framework is more modular and expandable. This change was<br>
proposed in commit 28fc6ba761ed4a47efa7c43e7f7dff<wbr>5e2fe72b5e<br>
"core-image-minimal-initramfs: use initramfs-framework by default" but<br>
reverted due to the selftests runqemu.RunqemuTests.test_boot<wbr>_machine_iso<br>
and runqemu.RunqemuTests.test_boot<wbr>_deploy_hddimg failing. Since then,<br>
the kinks have been worked out, and missing functionality that had been<br>
missed (non-EFI installation module) has been added.<br>
<br>
Since the PACKAGE_INSTALL variable was getting so long with all these<br>
individual modules getting added, I also introduced a new<br>
INITRAMFS_SCRIPTS variable to the core-image-minimal-initramfs recipe.<br>
This variable makes the recipe look much cleaner, and also allows easier<br>
replacement or additions to the scripts.<br>
<br>
Fixes [YOCTO #10987].<br>
<br>
Signed-off-by: California Sullivan <<a href="mailto:california.l.sullivan@intel.com" target="_blank">california.l.sullivan@intel.c<wbr>om</a>><br>
---<br>
meta/recipes-core/images/<a href="http://core-image-minimal-initramfs.bb" rel="noreferrer" target="_blank">core-<wbr>image-minimal-initramfs.bb</a> | 10 +++++++++-<br>
1 file changed, 9 insertions(+), 1 deletion(-)<br>
<br>
diff --git a/meta/recipes-core/images/<a href="http://core-image-minimal-initramfs.bb" rel="noreferrer" target="_blank">cor<wbr>e-image-minimal-initramfs.bb</a> b/meta/recipes-core/images/<a href="http://core-image-minimal-initramfs.bb" rel="noreferrer" target="_blank">cor<wbr>e-image-minimal-initramfs.bb</a><br>
index 5794a25952a..a9ba91bd310 100644<br>
--- a/meta/recipes-core/images/<a href="http://core-image-minimal-initramfs.bb" rel="noreferrer" target="_blank">cor<wbr>e-image-minimal-initramfs.bb</a><br>
+++ b/meta/recipes-core/images/<a href="http://core-image-minimal-initramfs.bb" rel="noreferrer" target="_blank">cor<wbr>e-image-minimal-initramfs.bb</a><br>
@@ -3,7 +3,15 @@ DESCRIPTION = "Small image capable of booting a device. The kernel includes \<br>
the Minimal RAM-based Initial Root Filesystem (initramfs), which finds the \<br>
first 'init' program more efficiently."<br>
-PACKAGE_INSTALL = "initramfs-live-boot initramfs-live-install initramfs-live-install-efi ${VIRTUAL-RUNTIME_base-utils} udev base-passwd ${ROOTFS_BOOTSTRAP_INSTALL}"<br>
+INITRAMFS_SCRIPTS ?= "\<br>
+ initramfs-framework-base \<br>
+ initramfs-module-setup-live \<br>
+ initramfs-module-udev \<br>
+ initramfs-module-install \<br>
+ initramfs-module-install-efi \<br>
+ "<br>
+<br>
+PACKAGE_INSTALL = "${INITRAMFS_SCRIPTS} ${VIRTUAL-RUNTIME_base-utils} udev base-passwd ${ROOTFS_BOOTSTRAP_INSTALL}"<br>
# Do not pollute the initrd image with rootfs features<br>
IMAGE_FEATURES = ""<br>
</blockquote>
<br>
</blockquote>
<br>
-- <br>
______________________________<wbr>_________________<br>
Openembedded-core mailing list<br>
<a href="mailto:Openembedded-core@lists.openembedded.org" target="_blank">Openembedded-core@lists.openem<wbr>bedded.org</a><br>
<a href="http://lists.openembedded.org/mailman/listinfo/openembedded-core" rel="noreferrer" target="_blank">http://lists.openembedded.org/<wbr>mailman/listinfo/openembedded-<wbr>core</a><br>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>