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>2018-12-08 17:17:37 +0000
commit55197b853d182911430ba141aca2c3ece07ba475 (patch)
treee635861083901b59973a6be290433cb38007d0c4 /bitbake
parent73e8104f9c07c0707964911b4882b55715104670 (diff)
downloadpoky-55197b853d182911430ba141aca2c3ece07ba475.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: 7a4e105093c3080c1087cd06abc2883852a23e28) 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 49973d6670..1a6a826746 100644
--- a/bitbake/lib/bb/server/process.py
+++ b/bitbake/lib/bb/server/process.py
@@ -400,7 +400,10 @@ class BitBakeServer(object):
400 os.close(self.readypipein) 400 os.close(self.readypipein)
401 401
402 ready = ConnectionReader(self.readypipe) 402 ready = ConnectionReader(self.readypipe)
403 r = ready.poll(30) 403 r = ready.poll(5)
404 if not r:
405 bb.note("Bitbake server didn't start within 5 seconds, waiting for 90")
406 r = ready.poll(90)
404 if r: 407 if r:
405 try: 408 try:
406 r = ready.get() 409 r = ready.get()