diff options
| author |   Richard Purdie <richard.purdie@linuxfoundation.org> | 2018-12-02 19:18:14 +0000 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2019-02-25 22:20:03 +0000 |
| commit | 64055fdb0d8485b40ba710a762e9a0af5c4540b4 (patch) | |
| tree | 13b93391709501cf9e0b0899e24d53ad160caf43 | |
| parent | 65c2a64d6dd5dc85cb14b9e808964c699e890517 (diff) | |
| download | bitbake-contrib-64055fdb0d8485b40ba710a762e9a0af5c4540b4.tar.gz | |
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.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
| -rw-r--r-- | lib/bb/server/process.py | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/lib/bb/server/process.py b/lib/bb/server/process.py index 0c6351d2e..a76b0a50c 100644 --- a/lib/bb/server/process.py +++ b/lib/bb/server/process.py @@ -398,7 +398,10 @@ class BitBakeServer(object): self.bitbake_lock.close() ready = ConnectionReader(self.readypipe) - r = ready.poll(30) + r = ready.poll(5) + if not r: + bb.note("Bitbake server didn't start within 5 seconds, waiting for 90") + r = ready.poll(90) if r: r = ready.get() if not r or r != "ready": |