[PATCH] sstate: change "stamp is not reachable, removing manifests" message from info to debug

[PATCH] sstate: change "stamp is not reachable, removing manifests" message from info to debug

[Ross Burton]

This code path has proven to work, so change the log level from info to debug so
it doesn't spam the log in normal use.

Signed-off-by: Ross Burton <ross.burton@intel.com>
---
 meta/classes/sstate.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes/sstate.bbclass b/meta/classes/sstate.bbclass
index 9bef212..9201146 100644
--- a/meta/classes/sstate.bbclass
+++ b/meta/classes/sstate.bbclass
@@ -952,7 +952,7 @@ 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)
         for r in toremove:
             (stamp, manifest, workdir) = r.split()
-- 
2.6.4

Re: [PATCH] sstate: change "stamp is not reachable, removing manifests" message from info to debug

[Trevor Woerner]

On 01/05/16 07:32, Ross Burton wrote:
> This code path has proven to work, so change the log level from info to debug so
> it doesn't spam the log in normal use.

I liked having this as part of the regular processing. If I only update
my upstream repositories once a week (for example) my next "bitbake ..."
would show which packages had upgrades. It was a cheap way of doing an
image diff, if you will.

In order to keep those messages now I would have to enable debug, which
will generate quite a lot more information.

Yes, I know I could get the "image diff" functionality by enabling
buildhistory and going that route, but as I said above this was sort of
a "cheap" image diff for free ;-)