From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Corneliu Stoicescu <corneliux.stoicescu@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] oe-selftest: New tests for sstate related operations
Date: Wed, 18 Dec 2013 16:55:24 +0000 [thread overview]
Message-ID: <3313957.6S11psWhHj@helios> (raw)
In-Reply-To: <1387277093-3051-1-git-send-email-corneliux.stoicescu@intel.com>
Hi Corneliu,
On Tuesday 17 December 2013 11:44:53 Corneliu Stoicescu wrote:
> Signed-off-by: Corneliu Stoicescu <corneliux.stoicescu@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
prev parent reply other threads:[~2013-12-18 16:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 10:44 [PATCH] oe-selftest: New tests for sstate related operations Corneliu Stoicescu
2013-12-18 16:55 ` Paul Eggleton [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3313957.6S11psWhHj@helios \
--to=paul.eggleton@linux.intel.com \
--cc=corneliux.stoicescu@intel.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox