From: Richard Purdie <rpurdie@linux.intel.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: Poky <poky@lists.pokylinux.org>
Subject: Re: Noexec tasks?
Date: Sun, 28 Nov 2010 12:13:40 +0000 [thread overview]
Message-ID: <1290946420.27143.49.camel@rex> (raw)
In-Reply-To: <4CE408E8.2030102@mlbassoc.com>
On Wed, 2010-11-17 at 09:55 -0700, Gary Thomas wrote:
> Messages like these are [fairly] new:
> NOTE: Noexec task 3045 of 3117 (ID: 505, /local/poky-amltd/meta/recipes-devtools/gcc/gcc-cross_4.5.0.bb, do_package_write)
> I don't see that they add much (any?) value and just increase the
> noise. For example, if I rerun 'bitbake some-image' which has N
> steps, I get N-2 of these followed by a couple of steps that actually
> do the work. Pretty annoying when N is large (for most images, N is
> measured in thousands of steps)
>
> Can these messages be suppressed? Is there any good reason to show them?
They're meant to appear once, the first time a noexec task is "skipped"
in the same way the other running task X of Y messages appear. I found
the bug that was causing the to repeat all the time and will push a fix
which should make the messages much less annoying :).
Cheers,
Richard
prev parent reply other threads:[~2010-11-28 21:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 16:55 Noexec tasks? Gary Thomas
2010-11-28 12:13 ` Richard Purdie [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=1290946420.27143.49.camel@rex \
--to=rpurdie@linux.intel.com \
--cc=gary@mlbassoc.com \
--cc=poky@lists.pokylinux.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