summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2020-03-01 10:54:55 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2020-03-02 16:16:22 +0000
commite66759106e21da2b34a6cdec7aa681ad2204da54 (patch)
treebcf251ef46a7d4b71f754cda7a978c67e4da07d5
parent47f0c849ed13ba554d9523b926d92405e8251702 (diff)
downloadbitbake-e66759106e21da2b34a6cdec7aa681ad2204da54.tar.gz
cooker: Reset parse status unpon clientComplete
If for example a tinfoil connection edits the datastore, a subsequent connection can be "corrupted" by those changes. By setting the parse status of the caches as False at exit, the behaviour becomes the same as a newly setup server as a new data store is setup. This avoids problems in tests when BB_SERVER_TIMEOUT is set as the server is properly reset between connections. [YOCTO #13812] Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--lib/bb/cooker.py2
1 files changed, 2 insertions, 0 deletions
diff --git a/lib/bb/cooker.py b/lib/bb/cooker.py
index 2d937a413..bda6d1b5c 100644
--- a/lib/bb/cooker.py
+++ b/lib/bb/cooker.py
@@ -1665,6 +1665,8 @@ class BBCooker:
self.command.reset()
self.databuilder.reset()
self.data = self.databuilder.data
+ self.parsecache_valid = False
+ self.baseconfig_valid = False
class CookerExit(bb.event.Event):