If you try to abort bitbake (with ^C) very early on, it will hang and external forces are required to kill it. >> $ bitbake some-image >> NOTE: Started PRServer with DBfile: >> /local/p7619_2016-02-23/cache/prserv.sqlite3, IP: 127.0.0.1, PORT: 43616, >> PID: 14386 Parsing recipes: 11% |########### >> >> | ETA: 00:00:21 >> >> Keyboard Interrupt, closing down... >> >> WARNING: Timeout while attempting to communicate with bitbake server >> WARNING: Timeout while attempting to communicate with bitbake server >> WARNING: Timeout while attempting to communicate with bitbake server >> WARNING: Timeout while attempting to communicate with bitbake server >> ERROR: Gave up; Too many tries: timeout while attempting to communicate with >> bitbake server >> >> Tested using poky:8debfea81e69d038bd2d56314b272cb74f5582ed This seems to only happen when there is no [initial] cache and may be very ephemeral as I was unable to make it happen on demand.
This was a hard one. Especially because it was hard for me to replicate it. Anyway, I think I fixed it: http://patchwork.openembedded.org/patch/119029/
Fix merged in: http://git.openembedded.org/bitbake/commit/?id=7ebea3e9a60232222efa8a546a0ff28a53029949
Verified on master.