summaryrefslogtreecommitdiffstats
path: root/bitbake/lib
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:27 +0000
commitfecd65625ec6fb9a7879cfa18eab95d2b1dda2ff (patch)
tree00c413a7cfc2572e27b77484ea839ab6ac955b92 /bitbake/lib
parentbed52fbf3cad0729688cc11883d5233eb5a4c6a0 (diff)
downloadpoky-fecd65625ec6fb9a7879cfa18eab95d2b1dda2ff.tar.gz
bitbake: 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] (Bitbake rev: e66759106e21da2b34a6cdec7aa681ad2204da54) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/lib')
-rw-r--r--bitbake/lib/bb/cooker.py2
1 files changed, 2 insertions, 0 deletions
diff --git a/bitbake/lib/bb/cooker.py b/bitbake/lib/bb/cooker.py
index 2d937a413c..bda6d1b5c4 100644
--- a/bitbake/lib/bb/cooker.py
+++ b/bitbake/lib/bb/cooker.py
@@ -1665,6 +1665,8 @@ class BBCooker:
1665 self.command.reset() 1665 self.command.reset()
1666 self.databuilder.reset() 1666 self.databuilder.reset()
1667 self.data = self.databuilder.data 1667 self.data = self.databuilder.data
1668 self.parsecache_valid = False
1669 self.baseconfig_valid = False
1668 1670
1669 1671
1670class CookerExit(bb.event.Event): 1672class CookerExit(bb.event.Event):