<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, May 18, 2015 at 1:08 PM, Lucas Dutra Nunes <span dir="ltr"><<a href="mailto:ldnunes@ossystems.com.br" target="_blank">ldnunes@ossystems.com.br</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="il">bitbake</span> uses a lock file on the build dir, "<span class="il">bitbake</span>.lock", to prevent it<br>
from running before an instance has exited. And sometimes the<br>
cleanup-workdir script can call bibake too many times, too fast, before<br>
the lock has been released.<br>
<br>
By simply waiting that the lock has been released solves this problem.<br>
<br>
Signed-off-by: Lucas Dutra Nunes <<a href="mailto:ldnunes@ossystems.com.br">ldnunes@ossystems.com.br</a>></blockquote></div><br>The fact that the bitbake UI can exit before the lock has been released is a bug. Not being able to assume bitbake is done by the time the bitbake command exits is not ideal, no one should have to block directly o the lock like this.<br>-- <br><div class="gmail_signature">Christopher Larson<br>clarson at kergoth dot com<br>Founder - BitBake, OpenEmbedded, OpenZaurus<br>Maintainer - Tslib<br>Senior Software Engineer, Mentor Graphics</div>
</div></div>