10238 2016-09-07 00:45:37 +0000 new runqemu fails when you change the DEPLOY_IMAGE_DIR variable for the test 2016-09-09 12:48:12 +0000 1 1 7 Build System, Metadata & Runtime OE-Core Scripts and Tools 2.2 x86 Multiple RESOLVED FIXED Medium+ normal 2.2 M3 1 brian.avery joshuagloe joshuagloe liezhi.yang ross.burton --- --- No (bug/feature does not impact docs) oldest_to_newest 65855 0 brian.avery 2016-09-07 00:45:37 +0000 Verified building for qemuppc but suspect it will fail for all archs. Changing the DEPLOY_DIR does NOT fail. To reproduce: $ bitbake core-image-sato-sdk (make sure you have INHERIT += "testimage" in conf) $ bitbake core-image-sato-sdk -c testimage (this should work) $ mv tmp/deploy/image/qemuppc/* /cow in local.conf set: DEPLOY_DIR_IMAGE="/cow" $ bitbake core-image-sato-sdk -c testimage (this should fail) and the failure should say something like: | NOTE: Output from runqemu: | runqemu - INFO - DEPLOY_DIR_IMAGE: /cow | runqemu - INFO - Assuming MACHINE = qemuppc | runqemu - INFO - Running MACHINE=qemuppc bitbake -e... | runqemu - ERROR - bitbake -e ERROR: Only one copy of bitbake should be run against a build directory | | runqemu - ERROR - Try 'runqemu help' on how to use it 65921 1 joshuagloe 2016-09-08 13:33:59 +0000 Confirmed. Even with the fixes for 10211[1] and 10240[2] I can reproduce this issue. We'll need to figure out how this works with the current, shell based, runqemu (which also usually invokes bitbake -e to determine bitbake variables) and create an equivalent change for the Python3 based runqemu. 1. https://bugzilla.yoctoproject.org/show_bug.cgi?id=10211 2. https://bugzilla.yoctoproject.org/show_bug.cgi?id=10240 65925 2 joshuagloe 2016-09-08 14:35:36 +0000 I've confirmed that this is a regression compared to the shell runqemu. 65954 3 joshuagloe 2016-09-08 20:50:57 +0000 http://lists.openembedded.org/pipermail/openembedded-core/2016-September/126346.html 65989 4 joshuagloe 2016-09-09 12:48:12 +0000 Fixed in OE-Core/Poky master