[bitbake-devel] [master][zeus][warrior][PATCH 2/2] cooker: Ignore notifications about changes to the sanity_info file

Peter Kjellerstedt peter.kjellerstedt at axis.com
Tue Jan 7 19:33:52 UTC 2020


Since this file is written during recipe parsing, having a watch on it
(or actually the directory that contains it) will trigger a re-parse
the next time bitbake is run and the resident bitbake server is
enabled. This causes the sanity_info file to be updated again, which
triggers a new re-parse the next time bitbake is run ad infinitum.

Also generalize the ignoring of bitbake-cookerdaemon.log and
bitbake.lock to all log files and lock files.

Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt at axis.com>
---
 bitbake/lib/bb/cooker.py | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/bitbake/lib/bb/cooker.py b/bitbake/lib/bb/cooker.py
index b74affa7ec..74c9fbc4c0 100644
--- a/bitbake/lib/bb/cooker.py
+++ b/bitbake/lib/bb/cooker.py
@@ -267,8 +267,9 @@ class BBCooker:
             self.parsecache_valid = False
             bb.parse.clear_cache()
             return
-        if event.pathname.endswith("bitbake-cookerdaemon.log") \
-                or event.pathname.endswith("bitbake.lock"):
+        if event.pathname.endswith(".log") \
+                or event.pathname.endswith(".lock") \
+                or event.pathname.endswith("sanity_info"):
             return
         if not event.pathname in self.inotify_modified_files:
             self.inotify_modified_files.append(event.pathname)
-- 
2.21.1



More information about the bitbake-devel mailing list