From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] insane bbclass: turn fatal errors back into fatal errors
Date: Thu, 30 Jun 2011 11:08:20 -0500 [thread overview]
Message-ID: <4E0C9F74.9040301@windriver.com> (raw)
In-Reply-To: <4E0C9D43.6020504@mentor.com>
On 6/30/11 10:58 AM, Tom Rini wrote:
> On 06/30/2011 08:11 AM, Koen Kooi wrote:
>> These were turned off by:
>>
>> commit fae8d5e985e9b05ce90f1eca434ad4dbf2259725
>> Author: Richard Purdie <rpurdie@linux.intel.com>
>> Date: Thu Jul 8 23:51:06 2010 +0100
>>
>> insane.bbclass: Relax fatal errors for now until we get have time to work through the backlog
>>
>> The current metadata triggers so many of these that they need to be made fatal so people will actually fix them.
>>
>> Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
>
> Given that a number of them can probably just be pulled from oe.dev as
> fixes too:
>
> Acked-by: Tom Rini <tom_rini@mentor.com>
I'm really worried about the current warnings/QA issues that keep coming up.. so
I agree we really need to do this.. (note, we also really need to tell people to
expect some breakage as we go and fix the mess!)
Acked-by: Mark Hatle <mark.hatle@windriver.com>
>> ---
>> meta/classes/insane.bbclass | 1 -
>> 1 files changed, 0 insertions(+), 1 deletions(-)
>>
>> diff --git a/meta/classes/insane.bbclass b/meta/classes/insane.bbclass
>> index f7e5524..e06d2b2 100644
>> --- a/meta/classes/insane.bbclass
>> +++ b/meta/classes/insane.bbclass
>> @@ -115,7 +115,6 @@ def package_qa_make_fatal_error(error_class, name, path,d):
>>
>> TODO: Load a whitelist of known errors
>> """
>> - return False
>> return not error_class in [0, 5, 7, 8, 9]
>>
>> def package_qa_write_error(error_class, name, path, d):
>
>
next prev parent reply other threads:[~2011-06-30 16:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 15:11 [PATCH] insane bbclass: turn fatal errors back into fatal errors Koen Kooi
2011-06-30 15:33 ` Paul Eggleton
2011-06-30 15:49 ` Koen Kooi
2011-06-30 15:59 ` Paul Eggleton
2011-07-01 16:25 ` Richard Purdie
2011-07-01 17:12 ` Richard Purdie
2011-07-01 17:16 ` Khem Raj
2011-07-01 17:25 ` Mark Hatle
2011-07-01 17:33 ` Koen Kooi
2011-07-01 18:18 ` Richard Purdie
2011-07-04 14:10 ` Paul Eggleton
2011-07-05 10:38 ` Richard Purdie
2011-07-01 14:55 ` Phil Blundell
2011-07-01 15:09 ` Koen Kooi
2011-06-30 15:58 ` Tom Rini
2011-06-30 16:08 ` Mark Hatle [this message]
2011-06-30 20:35 ` Koen Kooi
2011-06-30 20:59 ` Scott Garman
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=4E0C9F74.9040301@windriver.com \
--to=mark.hatle@windriver.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