diff options
| author |   Richard Purdie <richard.purdie@linuxfoundation.org> | 2023-06-30 18:04:11 +0100 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2023-06-30 18:05:25 +0100 |
| commit | a5c145f436d68f090b113cfb9b82857adc95b546 (patch) | |
| tree | ce5e4eeb0714ba0a86a61b5a9c14de7de7bda1ce | |
| parent | ac3cd866274f67b29eff89e393132bdabf76dbfd (diff) | |
| download | bitbake-contrib-a5c145f436d68f090b113cfb9b82857adc95b546.tar.gz | |
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.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
| -rw-r--r-- | lib/bb/cooker.py | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/lib/bb/cooker.py b/lib/bb/cooker.py index 0a21f1c2f..11c9fa2c4 100644 --- a/lib/bb/cooker.py +++ b/lib/bb/cooker.py @@ -1666,6 +1666,7 @@ class BBCooker: self.updateCacheSync() if self.state != state.parsing and not self.parsecache_valid: + bb.server.process.serverlog("Parsing started") self.setupParserWatcher() bb.parse.siggen.reset(self.data) |