[OE-core] [PATCH] oe-selftest: New tests for sstate related operations

Paul Eggleton paul.eggleton at linux.intel.com
Wed Dec 18 16:55:24 UTC 2013


Hi Corneliu,

On Tuesday 17 December 2013 11:44:53 Corneliu Stoicescu wrote:
> Signed-off-by: Corneliu Stoicescu <corneliux.stoicescu at intel.com>
> ---
>  meta/lib/oeqa/selftest/sstate.py |  226
> ++++++++++++++++++++++++++++++++++++++ 1 file changed, 226 insertions(+)
>  create mode 100644 meta/lib/oeqa/selftest/sstate.py
> 
> diff --git a/meta/lib/oeqa/selftest/sstate.py
> b/meta/lib/oeqa/selftest/sstate.py new file mode 100644
> index 0000000..d1fe20a
>...
> +        # buildhistory needs to be disabled for this test. It may report errors otherwise. 
> +        if 'buildhistory' in get_bb_var('USER_CLASSES'):
> +            remove_buildhistory_config = 'USER_CLASSES_remove = "buildhistory"' 
> +            self.append_config(remove_buildhistory_config)

I'm not sure this is the right way to go about this. buildhistory typically
wouldn't  be enabled via USER_CLASSES by the end user (since it's not 
the way we recommend in the manual, although there's no reason why it 
shouldn't work.) Assuming it's the "version going backwards" check that
is the problem, I'd suggest disabling the QA check instead like this:

ERROR_QA_remove = "version-going-backwards"

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



More information about the Openembedded-core mailing list