On Mon, May 18, 2015 at 7:23 PM, Christopher Larson <clar...@kergoth.com> wrote: > > > On Mon, May 18, 2015 at 1:08 PM, Lucas Dutra Nunes <ldnu...@ossystems.com.br> > 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 released. >> >> By simply waiting that the lock has been released solves this problem. >> >> Signed-off-by: Lucas Dutra Nunes <ldnu...@ossystems.com.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.
Agreed so you would prefer this to be fixed there? -- Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750 -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
