In current environment, we need to manually unset SANITY_TESTED_DISTROS whenever we need to run oe-selftest. The idea here is to make it part of oe-selftest execution to unset it automatically without additional editing by users.
There is a work on Bug 11401 with a patch directly setting this to local.conf but. that could be applied when Bug gets resolved 11429
*** Bug 11401 has been marked as a duplicate of this bug. ***
Created attachment 4392 [details] Automated to unset SANITY_TESTED_DISTORS
Issue solved by unset the SANITY_TESTED_DISTROS in the function OESelftestTestContextExecutor() file b/meta/lib/oeqa/selftest/context.py And added function remove_variables() which is called in final: self.remove_variables() the function will comment the the unset SANITY_TESTED_DISTROS in local.conf Source from the below patch https://hsdes.intel.com/appstore/article/#/1506456121 I am attaching my patch
Patches go the openembedded-core@lists.openembedded.org mailing list please, not bugzilla.
please ignore the comment 4 and comment 5 Issue solved by unset the SANITY_TESTED_DISTROS in the function OESelftestTestContextExecutor() file b/meta/lib/oeqa/selftest/context.py And added function remove_variables() which is called in final: self.remove_variables() the function will comment the the unset SANITY_TESTED_DISTROS in local.conf Source from the below patch https://patchwork.openembedded.org/patch/139410/
@Ross, as suggested, patch has been emailed to openembedded-core@lists.openembedded.org mailing list on 23 Nov'2018
Please add the link to the patch.
Bulk move from 4.99 or 0.00 to 5.99
v1 patch added here: https://patchwork.yoctoproject.org/project/oe-core/list/?series=28182 Discussion here: https://lists.openembedded.org/g/openembedded-core/topic/patch_oeqa_selftest/108807576 Will probably have a v2.
FORCE_VARIABLE is not RP's favourite but used more and more recently...