summaryrefslogtreecommitdiffstats
path: root/bitbake/lib/bb/cooker.py
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2023-06-30 18:04:11 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2023-06-30 18:05:30 +0100
commitd221e59a5067266c3f620259a1e56a56823df1fb (patch)
tree719fa52e6927d998a033fdf94661960282ab6c67 /bitbake/lib/bb/cooker.py
parent4bb1f0e236d27df861299c5fa689c18968690e88 (diff)
downloadpoky-d221e59a5067266c3f620259a1e56a56823df1fb.tar.gz
bitbake: cooker: Log when parsing starts in server log
It is unclear from the server logs when parsing starts. We know that timeouts sometimes happen when parsing but it is unclear where in the code the delays are from. Adding this debug message to the server log should help narrow that down. (Bitbake rev: a5c145f436d68f090b113cfb9b82857adc95b546) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/lib/bb/cooker.py')
-rw-r--r--bitbake/lib/bb/cooker.py1
1 files changed, 1 insertions, 0 deletions
diff --git a/bitbake/lib/bb/cooker.py b/bitbake/lib/bb/cooker.py
index 0a21f1c2f8..11c9fa2c40 100644
--- a/bitbake/lib/bb/cooker.py
+++ b/bitbake/lib/bb/cooker.py
@@ -1666,6 +1666,7 @@ class BBCooker:
1666 self.updateCacheSync() 1666 self.updateCacheSync()
1667 1667
1668 if self.state != state.parsing and not self.parsecache_valid: 1668 if self.state != state.parsing and not self.parsecache_valid:
1669 bb.server.process.serverlog("Parsing started")
1669 self.setupParserWatcher() 1670 self.setupParserWatcher()
1670 1671
1671 bb.parse.siggen.reset(self.data) 1672 bb.parse.siggen.reset(self.data)