<div dir="ltr"><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, 1 Nov 2019 at 18:46, Ross Burton <<a href="mailto:ross.burton@intel.com" target="_blank">ross.burton@intel.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Same failures on the Debian 10 worker:<br>
<br>
<a href="https://autobuilder.yoctoproject.org/typhoon/#/builders/56/builds/778" rel="noreferrer" target="_blank">https://autobuilder.yoctoproject.org/typhoon/#/builders/56/builds/778</a><br></blockquote><div><br></div><div><div dir="ltr"><div>runqemu - ERROR - Failed to run qemu: Xlib: extension "RANDR" missing on display ":1".<br>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.<br></div><div><br></div><div>Thanks - the Gtk part is passing fine, so it's something SDL does that upsets the X/GL stack on the Debian 10 host.</div><div>I am reluctant to disable the SDL part of the virgl tests on Debian 10, as it is a new distro (unlike centos 7).<br></div><div><br></div><div>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?<br></div><div><br></div><div>Alex<br></div></div> </div></div>
</div>