Hi Richard, Noted with the changes. I had try to reproduce the same failure log that you send to me. However, the result is different.
How can I run the oe-selftest to test out the patch on my machine correctly? Can you verify with me whether the steps below are the correct steps? Firstly git clone a poky and meta-intel layer, then source a build. I also enable the oe-selftest configuration on my local.conf and run the command "oe-selftest -r runqemu.RunqemuTests.test_boot_deploy_hddimg"? I try to test the latest poky master branch without my "use initramfs-framework by default" commit, the oe-selftest for those two testcases are failed too) Here is the failure log that I captured: http://pastebin.intel.com/hefizelixo.vhdl Regards, Wei Tee -----Original Message----- From: Richard Purdie [mailto:richard.pur...@linuxfoundation.org] Sent: Sunday, July 30, 2017 3:48 PM To: Ng, Wei Tee <wei.tee...@intel.com>; openembedded-core@lists.openembedded.org Cc: Wold, Saul <saul.w...@intel.com> Subject: Re: [OE-core] [PATCH 3/3] core-image-minimal-initramfs: use initramfs-framework by default On Sun, 2017-07-23 at 16:51 -0700, wei.tee...@intel.com wrote: > From: "Ng, Wei Tee" <wei.tee...@intel.com> > > Use the initramfs-framework for initialization by default due to the > modularity and expansibility. > > [YOCTO #10987] > > Signed-off-by: Ng, Wei Tee <wei.tee...@intel.com> > --- > meta/recipes-core/images/core-image-minimal-initramfs.bb | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) I'm afraid I had to revert this change: http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=fab2219af4a6566124 cf95d1d2648d4729391baf because it was causing oe-selftest failures as shown here: https://autobuilder.yocto.io/builders/nightly-oe-selftest/builds/415/st eps/Running%20oe-selftest/logs/stdio Cheers, Richard -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
