Bug 10240 - Python3 runqemu doesn't support calling testimage on QEMU artefacts copied from another host/build dir
Summary: Python3 runqemu doesn't support calling testimage on QEMU artefacts copied fr...
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: Scripts and Tools (show other bugs)
Version: 2.2
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 2.2 M3
Assignee: Joshua Lock
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-09-07 16:18 UTC by Joshua Lock
Modified: 2016-09-09 12:48 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joshua Lock 2016-09-07 16:18:15 UTC
One use-case that used to work but no longer does in the Python 3 runqemu rewrite is to copy build artefacts and then invoke bitbake <relevant-image> -c testimage.

Because bitbake is already running the runqemu script can't call `bitbake -e` in order to determine the paths to staging directories.

The old runqemu used which to locate relevant binaries, we could add that as a fallback path in the new runqemu.
Comment 2 Joshua Lock 2016-09-09 12:48:41 UTC
Fixed in OE-Core/Poky master