oe-selftest: Error if known problem variables are set

Setting SANITY_TESTED_DISTROS or PRSERV_HOST are known to break oe-selftest.
Rather than have the user experience this, refuse to execute unless the
environment is correct.

Ideally we'd try and unset these but that is a more invasive change and this
at least makes people aware of the problem.

[YOCTO #11292]

(From OE-Core rev: 0c9b981e88c76da316e76f17e6da3a03b87c5008)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Richard Purdie 2017-04-12 19:54:20 +01:00
parent 3f32ca2a57
commit ffabe5d1b9
1 changed files with 8 additions and 0 deletions

View File

@ -146,6 +146,14 @@ def preflight_check():
log.error("You have buildhistory enabled already and this isn't recommended for selftest, please disable it first.") log.error("You have buildhistory enabled already and this isn't recommended for selftest, please disable it first.")
return False return False
if get_bb_var("PRSERV_HOST"):
log.error("Please unset PRSERV_HOST in order to run oe-selftest")
return False
if get_bb_var("SANITY_TESTED_DISTROS"):
log.error("Please unset SANITY_TESTED_DISTROS in order to run oe-selftest")
return False
log.info("Running bitbake -p") log.info("Running bitbake -p")
runCmd("bitbake -p") runCmd("bitbake -p")