Hi Richard Thanks for the update!
On Sat, Apr 25, 2020 at 11:07 PM Richard Purdie <richard.pur...@linuxfoundation.org> wrote: > > On Thu, 2020-04-23 at 15:17 +0200, Ricardo Ribalda Delgado wrote: > > On my setup, using debian crops the error is even different :( > > > > If you want I can keep trying, otherwise I will leave it to the > > experts ;) > > Just to update, I bisected this down to my sysroot patches in master- > next. Which makes no sense, how would sysroot changes cause wic to fail > in runqemu? > > I've discovered that you have to run two tests in the same build one > after the other, specifically: > > oe-selftest -r devtool.DevtoolExtractTests.test_devtool_deploy_target > wic.Wic2.test_qemu_efi > > and I think my sysroot change "causes" problems as it adds a new test > class. This reorders tests and triggers this magic order problem. I > haven't confirmed but I think the above will fail without my patch. > > The key is the wic test failing with: > > FileNotFoundError: [Errno 2] No such file or directory: > '/media/build1/poky/build-st/tmp/work/qemux86_64-poky-linux/oe-selftest-image/1.0-r0/testimage/qemurunner_log.20200425200658' > > i.e. why is it writing to oe-selftest-image which is only used by the > devtool test? > > The answer is I think the runqemu code is leaking logfile handles > somehow. > > At least now we have a simpler and consistent reproducer and some idea > of the problem this should be easier to track down. 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. 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? 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? Thanks > > Cheers, > > Richard > > > -- Ricardo Ribalda
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#137487): https://lists.openembedded.org/g/openembedded-core/message/137487 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] -=-=-=-=-=-=-=-=-=-=-=-
