From: Robert Yang <liezhi.yang@windriver.com>
To: Ross Burton <ross.burton@intel.com>,
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] sstate: replace verbose manifest removal with a single count
Date: Thu, 21 Jan 2016 16:33:14 +0800 [thread overview]
Message-ID: <56A097CA.1070703@windriver.com> (raw)
In-Reply-To: <1453134365-26107-1-git-send-email-ross.burton@intel.com>
On 01/19/2016 12:26 AM, Ross Burton wrote:
> If there are lots of changes between the previous build and the build about to
> start bitbake will potentially print pages of:
>
> DEBUG: Stamp $BUILD/stamps/corei7-64-poky-linux/libdrm/2.4.66-r0 is not reachable, removing related manifests
>
> Instead of spamming the console with this list, write the list of manifests only
> to the debug log and simply write a count to the console. This way the user
> doesn't get spammed but still knows what is happening if bitbake appears to
> stall with heavy I/O.
>
> Signed-off-by: Ross Burton <ross.burton@intel.com>
> ---
> meta/classes/sstate.bbclass | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/meta/classes/sstate.bbclass b/meta/classes/sstate.bbclass
> index 9bef212..918768f 100644
> --- a/meta/classes/sstate.bbclass
> +++ b/meta/classes/sstate.bbclass
> @@ -952,8 +952,12 @@ python sstate_eventhandler2() {
> if stamp not in stamps:
> toremove.append(l)
> if stamp not in seen:
> - bb.note("Stamp %s is not reachable, removing related manifests" % stamp)
> + bb.debug(2, "Stamp %s is not reachable, removing related manifests" % stamp)
> seen.append(stamp)
> +
> + if toremove:
> + bb.note("There are %d recipes to be removed from the sysroot, removing..." % (len(toremove)))
> +
Currently, I get:
NOTE: There are 10 recipes to be removed from the sysroot, removing...
NOTE: There are 15 recipes to be removed from the sysroot, removing...
NOTE: There are 30 recipes to be removed from the sysroot, removing...
Can we print more info such as where it is removing, please ? Or
use SSTATE_ARCHS ? For example,:
NOTE: There are 30 recipes to be removed from manifest x86_64, removing...
// Robert
> for r in toremove:
> (stamp, manifest, workdir) = r.split()
> for m in glob.glob(manifest + ".*"):
>
next prev parent reply other threads:[~2016-01-21 8:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 16:26 [PATCH] sstate: replace verbose manifest removal with a single count Ross Burton
2016-01-21 8:33 ` Robert Yang [this message]
2016-01-21 12:19 ` Burton, Ross
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=56A097CA.1070703@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@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