Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Cc: Chris Larson <clarson@kergoth.com>
Subject: Re: Tell me your build error message annoyances!
Date: Mon, 06 Jun 2011 21:53:18 -0700	[thread overview]
Message-ID: <4DEDAEBE.8080404@linux.intel.com> (raw)
In-Reply-To: <BANLkTi=n+MNMu+EY0F5Hh3OqVe7Ex7CCQg@mail.gmail.com>



On 06/03/2011 08:47 AM, Chris Larson wrote:
> On Fri, Jun 3, 2011 at 8:43 AM, Phil Blundell <pb@pbcl.net> wrote:
>> On Fri, 2011-06-03 at 09:22 -0500, Mark Hatle wrote:
>>> I believe currently we have around 3-5 messages per step, and it's still too
>>> noisy -- unless you need to debug something.
>>
>> Correct.  Right now, the output looks like:
>>
>> NOTE: Running task 613 of 728 (ID: 190, virtual:native:/home/pb/oe/oe-core/meta/recipes-core/util-linux/util-linux_2.19.1.bb, do_install)
>> NOTE: package util-linux-native-2.19.1-r0: task do_install: Started
>> NOTE: package util-linux-native-2.19.1-r0: task do_install: Succeeded
>> NOTE: Running task 614 of 728 (ID: 191, virtual:native:/home/pb/oe/oe-core/meta/recipes-core/util-linux/util-linux_2.19.1.bb, do_populate_sysroot)
>> NOTE: package util-linux-native-2.19.1-r0: task do_populate_sysroot: Started
>> NOTE: package util-linux-native-2.19.1-r0: task do_populate_sysroot: Succeeded
>>
>> It looks as though the "Started" and "Succeeded" lines could just be
>> deleted without losing any real information.
> 
> Heh, I used to have a personal branch where I dropped those, and also
> removed the unnecessary NOTE: prefix. I think its a given that
> something that doesn't indicate a warning or an error is simply
> informative :) The problem with dropping those messages is for
> postprocessing scripts, which may well want/need to know when a task
> completes, not just when it starts. Still, yet another case of
> something we could drop as long as we log it. We need to add a main
> bitbake execution log that captures everything, including debug
> messages, whether the user specifies -D or not.

In most systems, running with -D implies not only greater verbosity, but
also reduced performance. I haven't checked, but I expect that is the
case with bitbake as well. I don't think we want to enable all of -D and
log it by default.

Thanks,

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel



  reply	other threads:[~2011-06-07  4:56 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-31 22:26 Tell me your build error message annoyances! Scott Garman
2011-06-01  1:34 ` mark gross
2011-06-01 15:06 ` Phil Blundell
2011-06-01 16:25   ` Richard Purdie
2011-06-01 16:58     ` Chris Larson
2011-06-03 14:35     ` mark gross
2011-06-03 14:48       ` Paul Eggleton
2011-06-02 14:17   ` Phil Blundell
2011-06-02  7:34 ` Martin Jansa
2011-06-03  6:10 ` Darren Hart
2011-06-03  8:11   ` Richard Purdie
2011-06-03 14:22   ` Mark Hatle
2011-06-03 15:43     ` Phil Blundell
2011-06-03 15:47       ` Chris Larson
2011-06-07  4:53         ` Darren Hart [this message]
2011-06-07  9:18           ` Richard Purdie
2011-06-06 21:13   ` Scott Garman
2011-06-03 14:57 ` Koen Kooi
2011-06-09 11:02 ` Phil Blundell
2011-06-09 11:17   ` Richard Purdie
2011-06-09 15:00 ` 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=4DEDAEBE.8080404@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=clarson@kergoth.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