summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRoss Burton <ross.burton@intel.com>2016-01-18 16:22:01 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2016-01-19 17:37:24 +0000
commite777b541c76dad293d1c214e46c00f8f78fe0539 (patch)
treead5e1019152aaf86eda41d49abefa3419be9bbdf
parent018bc5121c70ff1f609d5b3406401902b7e7b2f7 (diff)
downloadopenembedded-core-contrib-e777b541c76dad293d1c214e46c00f8f78fe0539.tar.gz
openembedded-core-contrib-e777b541c76dad293d1c214e46c00f8f78fe0539.tar.bz2
openembedded-core-contrib-e777b541c76dad293d1c214e46c00f8f78fe0539.zip
sstate: replace verbose manifest removal with a single count
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>
-rw-r--r--meta/classes/sstate.bbclass6
1 files changed, 5 insertions, 1 deletions
diff --git a/meta/classes/sstate.bbclass b/meta/classes/sstate.bbclass
index 804629199f..40b51fe4fe 100644
--- a/meta/classes/sstate.bbclass
+++ b/meta/classes/sstate.bbclass
@@ -956,8 +956,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)))
+
for r in toremove:
(stamp, manifest, workdir) = r.split()
for m in glob.glob(manifest + ".*"):