Bug 11443

Summary: QemuRunner: should not modify os.environ
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Patrick Ohly <patrick.ohly>
Component: deploymentAssignee: Patrick Ohly <patrick.ohly>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Medium+ CC: mikko.ylinen, richard.purdie
Version: unspecified   
Target Milestone: 2.4 M1   
Hardware: x86   
OS: Multiple   
Whiteboard: Backport to 2.3.1
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Patrick Ohly 2017-05-03 10:04:37 UTC 
In Refkit we wrote some oe-selftest tests which use oeqa.utils.commands.runqemu() to run qemu with different DEPLOY_DIR_IMAGE values (the real one in some cases, a manually constructed one in another). The artificial directory leaked from one test to another.

I'm pretty sure now the root cause is that QemuRunner modifies the process state permanently by setting os.environ["DEPLOY_DIR_IMAGE"] and other env variables. It really shouldn't be doing that.
Comment 1 Patrick Ohly 2017-05-03 11:16:21 UTC 
Patch sent: "[PATCH] QemuRunner: avoid tainting os.environ"