summaryrefslogtreecommitdiffstats
path: root/bitbake
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2025-03-10 14:53:47 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2025-03-11 10:53:13 +0000
commitec166484a2b2a15d0855ca152a019a64357d631d (patch)
treee636ccee6eb6afe7c0b61211baee2cf19944f0e7 /bitbake
parent046a92d351e2025e0dadead9f70f85eff8f5af70 (diff)
downloadpoky-ec166484a2b2a15d0855ca152a019a64357d631d.tar.gz
bitbake: cooker: Add debug for parsing being complete
We have a "parsing started" event in the cooker deamon log but we don't currently log the corresponding "parsing complete" event which is confusing. Add this so that the logs are more logical. (Bitbake rev: 1aa491c1f1211bf9faab712c321b66629fb7be66) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake')
-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 e21815daad..1810bcc604 100644
--- a/bitbake/lib/bb/cooker.py
+++ b/bitbake/lib/bb/cooker.py
@@ -1636,6 +1636,7 @@ You can also remove the BB_HASHSERVE_UPSTREAM setting, but this may result in si
1636 self.state = State.PARSING 1636 self.state = State.PARSING
1637 1637
1638 if not self.parser.parse_next(): 1638 if not self.parser.parse_next():
1639 bb.server.process.serverlog("Parsing completed")
1639 collectlog.debug("parsing complete") 1640 collectlog.debug("parsing complete")
1640 if self.parser.error: 1641 if self.parser.error:
1641 raise bb.BBHandledException() 1642 raise bb.BBHandledException()