summaryrefslogtreecommitdiffstats
path: root/bitbake
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2018-12-02 19:18:14 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2019-02-25 22:27:46 +0000
commit245e1c251a6993733fbf4a8fdb931e0cc05e47c0 (patch)
tree7c795d552f10896542ee2e473209ab218796f3bb /bitbake
parentcaad85d90b18f010b2fe7766335ba3213da7ee27 (diff)
downloadpoky-245e1c251a6993733fbf4a8fdb931e0cc05e47c0.tar.gz
bitbake: server/process: Increase server startup time delay
On loaded production systems we've seen bitbake server take over 40s to start up. Increase the timeout to 90s which tries to avoid failures in selftests. The delays come from setting up the inotify watches (31s) so can't really be avoided. After 5s delay we now warn the user we're waiting for 90s so the interactive exeperience shouldn't be much changed and its very unlikely the user would see that anyway. (Bitbake rev: 64055fdb0d8485b40ba710a762e9a0af5c4540b4) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake')
-rw-r--r--bitbake/lib/bb/server/process.py5
1 files changed, 4 insertions, 1 deletions
diff --git a/bitbake/lib/bb/server/process.py b/bitbake/lib/bb/server/process.py
index 0c6351d2e8..a76b0a50c7 100644
--- a/bitbake/lib/bb/server/process.py
+++ b/bitbake/lib/bb/server/process.py
@@ -398,7 +398,10 @@ class BitBakeServer(object):
398 self.bitbake_lock.close() 398 self.bitbake_lock.close()
399 399
400 ready = ConnectionReader(self.readypipe) 400 ready = ConnectionReader(self.readypipe)
401 r = ready.poll(30) 401 r = ready.poll(5)
402 if not r:
403 bb.note("Bitbake server didn't start within 5 seconds, waiting for 90")
404 r = ready.poll(90)
402 if r: 405 if r:
403 r = ready.get() 406 r = ready.get()
404 if not r or r != "ready": 407 if not r or r != "ready":