All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] context: allow test execution with buildhistory unless version-going-backwards is present
Date: Fri, 23 Jun 2017 09:17:13 -0500	[thread overview]
Message-ID: <1498227433.31575.79.camel@linux.intel.com> (raw)
In-Reply-To: <20170608204022.427-1-leonardo.sandoval.gonzalez@linux.intel.com>

The proposed approach is not the best one as discussed by RP [1]:

""Just as another note, 

ERROR_QA_remove = "version-going-backwards"
WARN_QA_remove = "version-going-backwards"

doesn't work since we can't then enable this check and the test cases
test_buildhistory_buildtime_pr_backwards and test_buildhistory_diff then
fail."

[1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=11580#c7


On Thu, 2017-06-08 at 13:40 -0700,
leonardo.sandoval.gonzalez@linux.intel.com wrote:
> From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
> 
> Users constantly running oe-selftest find annoying to disable buildhistory before running
> 'oe-selftest' then enabling after it. To lessen the buildhistory restriction, allow buildhistory
> unless 'version-going-backwards' is present on ERROR_QA bitbake variable.
> 
> [YOCTO #11580]
> 
> Signed-off-by: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
> ---
>  meta/lib/oeqa/selftest/context.py | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/meta/lib/oeqa/selftest/context.py b/meta/lib/oeqa/selftest/context.py
> index ca73070c0b..f061b987b0 100644
> --- a/meta/lib/oeqa/selftest/context.py
> +++ b/meta/lib/oeqa/selftest/context.py
> @@ -150,7 +150,8 @@ class OESelftestTestContextExecutor(OETestContextExecutor):
>          _check_required_env_variables(["BUILDDIR"])
>          _check_presence_meta_selftest()
>  
> -        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']:
>              self.tc.logger.error("You have buildhistory enabled already and this isn't recommended for selftest, please disable it first.")
>              raise OEQAPreRun
>  




      parent reply	other threads:[~2017-06-23 14:08 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
2017-06-23 14:17 ` Leonardo Sandoval [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=1498227433.31575.79.camel@linux.intel.com \
    --to=leonardo.sandoval.gonzalez@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.