On Sat, 2020-04-25 at 23:25 +0200, Ricardo Ribalda Delgado wrote:
> I have also been working on the issue, and eventhought I have not
> been
> able to replicate locally the bug, the code insspection was pointing
> to the same direction.
> My running hypothesis is that the logger keeps writting to the
> filehandler because nobody has removed it, so the second time we use
> qemu, the log file is missing and all dies
> 
> 
> Eg: Here I cannot see where the handler is removed
> https://git.openembedded.org/openembedded-core/tree/meta/lib/oeqa/targetcontrol.py?h=master-next#n122
> 
> 
> Eg: Here I can
> 
> https://git.openembedded.org/openembedded-core/tree/meta/lib/oeqa/utils/commands.py#n353
> 
> 
> Unfortunately, as I said, I cannot replicate it, so it is a bit
> frustrating.

The line I gave in the last email should reproduce it reliably. The key
is to have a runqemu session which you then clean the image for
(devtool does), then a write happens to a directory which no longer
exists from the logging.

> Since you can replicate it, could I send you a couple of patches, not
> to fix it, but to find out if I am on the right direction?

Since my other email I couldn't resist poking at the code. Locally this
patch fixed it so its now also running on the autobuilder:

http://git.yoctoproject.org/cgit.cgi/poky/commit/?h=master-next&id=3e7d64adba65559e9b8af42e973c8524988b216a

> Can you also publish a git branch somewhere with the current error,
> so we work on the same codebase?
> 
> Or you just prefer to continue on your own?

Happy to have help but I'm simply using master-next and with any luck I
might have found it.

Cheers,

Richard



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#137489): 
https://lists.openembedded.org/g/openembedded-core/message/137489
Mute This Topic: https://lists.openembedded.org/mt/73123269/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to