Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] context: allow test execution with buildhistory unless version-going-backwards is present
Date: Fri, 09 Jun 2017 09:19:47 -0500	[thread overview]
Message-ID: <1497017987.26945.178.camel@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LZHv-h9Kna7o1HXc8n+XaxTbYtW_=+vbFOd79KgKD=-tA@mail.gmail.com>

On Fri, 2017-06-09 at 13:51 +0100, Burton, Ross wrote:
> 
> On 8 June 2017 at 21:40, <leonardo.sandoval.gonzalez@linux.intel.com>
> wrote:
>         -        if "buildhistory.bbclass" in
>         self.tc.td["BBINCLUDED"]:
>         +        # buildhistory introduce QA 'version-going-backwards'
>         errors so stop if the latter are enabled
>         +        if "buildhistory.bbclass" in self.tc.td["BBINCLUDED"]
>         and 'version-going-backwards' in self.tc.td['ERROR_QA']:
>         
> 
> Would it be possible instead to remove version-going-backwards from
> ERROR_QA?

At the bug entry, there is a discussion around this. The idea is to keep
buildhistory disable while oe-selftest is executing, but if user really
needs this, 'force' the user to remove this check from the ERROR_QA
string on his/her local.conf.
> 
> 
> Ross




  reply	other threads:[~2017-06-09 14:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-08 20:40 [PATCH] context: allow test execution with buildhistory unless version-going-backwards is present leonardo.sandoval.gonzalez
2017-06-09 12:51 ` Burton, Ross
2017-06-09 14:19   ` Leonardo Sandoval [this message]
2017-06-23 14:17 ` Leonardo Sandoval

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=1497017987.26945.178.camel@linux.intel.com \
    --to=leonardo.sandoval.gonzalez@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /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