On 18 May 2015 at 23:23, Christopher Larson wrote:
> 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.
>
A
* Otavio Salvador [150519 00:27]:
> On Mon, May 18, 2015 at 7:23 PM, Christopher Larson
> wrote:
> > On Mon, May 18, 2015 at 1:08 PM, Lucas Dutra Nunes
> > wrote:
> >> bitbake uses a lock file on the build dir, "bitbake.lock", to prevent it
> >> from running before an instance has exited. A
On Mon, May 18, 2015 at 7:23 PM, Christopher Larson wrote:
>
>
> On Mon, May 18, 2015 at 1:08 PM, Lucas Dutra Nunes
> wrote:
>>
>> bitbake uses a lock file on the build dir, "bitbake.lock", to prevent it
>> from running before an instance has exited. And sometimes the
>> cleanup-workdir script c
On Mon, May 18, 2015 at 1:08 PM, Lucas Dutra Nunes wrote:
> bitbake uses a lock file on the build dir, "bitbake.lock", to prevent it
> from running before an instance has exited. And sometimes the
> cleanup-workdir script can call bibake too many times, too fast, before
> the lock has been releas
bitbake uses a lock file on the build dir, "bitbake.lock", to prevent it
from running before an instance has exited. And sometimes the
cleanup-workdir script can call bibake too many times, too fast, before
the lock has been released.
By simply waiting that the lock has been released solves this p
