All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Mueller <schnitzeltony@gmx.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: bitbake does not fail when QA issues encountered
Date: Fri, 4 Feb 2011 14:58:18 +0100	[thread overview]
Message-ID: <201102041458.18471.schnitzeltony@gmx.de> (raw)
In-Reply-To: <AANLkTi=7X86Wvps_HETYz7mkCSZbDKLxBHP1uW6NUbMN@mail.gmail.com>

On Friday 04 February 2011 14:10:33 Frans Meulenbroeks wrote:
> 2011/2/4 Otavio Salvador <otavio@ossystems.com.br>:
> > On Fri, Feb 4, 2011 at 09:57, Frans Meulenbroeks
> > <fransmeulenbroeks@gmail.com> wrote:
> >> Actually I did not react on the libtool forcing upon everyone, but on
> >> the QA errors (where this thread was about).
> >> That was also the cause of the ostrich remark (which was definitely
> >> not aimed at you in person, but more a general comment, triggered by
> >> the fact that I have some experience with projects being outsourced to
> >> an unnamed country where a bug report also could be "repaired" by
> >> removing the message or the the symptom instead of tackling the root
> >> cause).
> >>
> >> What I see is a lack of interest in fixing the existing QA errors.
> >> I've sent out a few error reports to the list a while ago, (on recipes
> >> that I feel not comfortable with), but unfortunately that did not
> >> result in any action :-(
> >
> > I think we ought to FAIL on QA errors. Distros can ignore the errors
> > if they want but OE as a whole cannot do that.
> 
> I tend to agree with this.
> Actually it would be nice if insane.bbclass would allow a way to
> specify which tests you want to do.
My suggestion: Run alI tests but make it configurable what causes just warnings 
and what causes errors (not too many options e.g. all QA cause errors or 
warning). There are different roles: OE-Users do not want the build to be 
broken - images with QA errors might run without errors. OE developers might
appreciate to get a hard error for the package currently working on or for test 
builds.

Andreas




  reply	other threads:[~2011-02-04 14:02 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-25 19:37 bitbake does not fail when QA issues encountered Maupin, Chase
2011-01-25 20:58 ` Frans Meulenbroeks
2011-01-25 21:36   ` Khem Raj
2011-01-26 10:32     ` Martyn Welch
2011-01-26 15:03       ` Maupin, Chase
2011-01-26 15:27         ` Tom Rini
2011-01-27  9:38           ` Thomas Zimmermann
2011-01-27 11:27             ` Frans Meulenbroeks
2011-01-27 15:02               ` Tom Rini
2011-02-03  7:09                 ` Denys Dmytriyenko
2011-02-03 17:43                   ` Tom Rini
2011-02-03 22:20                     ` Denys Dmytriyenko
2011-02-03 23:09                       ` Tom Rini
2011-02-04  7:54                         ` Frans Meulenbroeks
2011-02-04  8:16                           ` Stefan Schmidt
2011-02-04  8:37                             ` Frans Meulenbroeks
2011-02-04  9:03                               ` Stefan Schmidt
2011-02-04  9:57                                 ` Frans Meulenbroeks
2011-02-04 12:42                                   ` Otavio Salvador
2011-02-04 13:10                                     ` Frans Meulenbroeks
2011-02-04 13:58                                       ` Andreas Mueller [this message]
2011-02-04 14:59                                   ` Tom Rini
2011-02-04 15:26                                     ` Frans Meulenbroeks
2011-02-04 15:52                                       ` Otavio Salvador
2011-02-05 13:35                                         ` Frans Meulenbroeks
2011-02-06  1:21                                           ` Otavio Salvador
2011-02-06 12:02                                             ` Frans Meulenbroeks
2011-02-09 20:02                                           ` Maupin, Chase
2011-02-09 20:13                                           ` Maupin, Chase
2011-02-10  6:32                                             ` Frans Meulenbroeks
2011-02-04 17:37                                       ` Tom Rini
2011-02-04 14:44                     ` Tom Rini

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=201102041458.18471.schnitzeltony@gmx.de \
    --to=schnitzeltony@gmx.de \
    --cc=openembedded-devel@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.