[OE-core] [PATCH 3/6] oe-selftest: extend virgl gtk test to also check the SDL option

[Alexander Kanavin]

On Sat, 2 Nov 2019 at 13:07, Alexander Kanavin <alex.kanavin at gmail.com>
wrote:

> Same failures on the Debian 10 worker:
>
>>
>> https://autobuilder.yoctoproject.org/typhoon/#/builders/56/builds/778
>>
>
> runqemu - ERROR - Failed to run qemu: Xlib:  extension "RANDR" missing on
> display ":1".
> qemu-system-x86_64: ../libepoxy-1.5.3/src/dispatch_common.c:863:
> epoxy_get_proc_address: Assertion `0 && "Couldn't find current GLX or EGL
> context.\n"' failed.
>
> Thanks - the Gtk part is passing fine, so it's something SDL does that
> upsets the X/GL stack on the Debian 10 host.
> I am reluctant to disable the SDL part of the virgl tests on Debian 10, as
> it is a new distro (unlike centos 7).
>
> I'll try to see if I can run Debian 10 in a VM here and try to reproduce.
> Or is it possible to debug directly on a Debian 10 worker?
>

So I actually went ahead, and installed Debian 10 into a qemu image, then
transferred a pre-populated build directory into it, and ran runqemu there
against tigervnc (hurray for the nested kvm feature!).

Both 'runqemu kvm sdl gl' and 'runqemu kvm gtk gl' work fine, including
running kmscube!

So I'd like to see what packages are installed on the Debian 10 worker vs.
my Debian 10 installation.

Can you issue 'dpkg -l' on the worker, and send me the output, please?
Maybe something is missing?

Alex
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20191102/44379343/attachment.html>