Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] Revert "bitbake.conf: don't remove WARN_QA and ERROR_QA from hashes"
Date: Fri, 6 Feb 2015 16:02:41 +0100	[thread overview]
Message-ID: <20150206150241.GG2287@jama> (raw)
In-Reply-To: <CAP9ODKoE12hnigK3Z1MKjV5TYRu-EACd2KsCgD0M2hZSEFeNww@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1191 bytes --]

On Fri, Feb 06, 2015 at 12:21:23PM -0200, Otavio Salvador wrote:
> On Fri, Feb 6, 2015 at 12:18 PM, Burton, Ross <ross.burton@intel.com> wrote:
> >
> > On 6 February 2015 at 14:10, Otavio Salvador <otavio@ossystems.com.br>
> > wrote:
> >>
> >> I think they should re-run. Otherwise we can end having errors and QA
> >> issues unnoticed until a full rebuild.
> >
> >
> > That was the state of things until my original patch last week.  The patch
> > had the side-effect that changing QA tasks causing *everything* to rebuild.
> > I'm really not sure that's a good solution.
> 
> If someone adds a QA tasks it is because it matters. In this case we
> ought to have it in an immediate effect so it does makes sense to
> rerun everything.
> 
> I know it is bad from build time point of view but predictability and
> correctness is more important from my point of view.

Agreed, especially when someone decides to make something fatal it
should highlight all failing recipes before it's enabled in "official"
build instead of sneaking the failures one-by-one as sstate is being
invalidated by other changes.

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2015-02-06 15:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-04 21:33 [PATCH] Revert "bitbake.conf: don't remove WARN_QA and ERROR_QA from hashes" Ross Burton
2015-02-06 10:41 ` Paul Eggleton
2015-02-06 11:42   ` Richard Purdie
2015-02-06 14:10     ` Otavio Salvador
2015-02-06 14:18       ` Burton, Ross
2015-02-06 14:21         ` Otavio Salvador
2015-02-06 15:02           ` Martin Jansa [this message]
2015-02-06 15:13             ` Richard Purdie
2015-02-06 15:53               ` Otavio Salvador
2015-02-06 16:29                 ` Paul Eggleton

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=20150206150241.GG2287@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    --cc=paul.eggleton@linux.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