Hi On Mon, Jun 27, 2022 at 7:14 AM Richard Henderson < richard.hender...@linaro.org> wrote:
> Hi Mark, > > > + def test_virtio_vga_virgl(self): > > > + """ > > > + :avocado: tags=arch:x86_64 > > > + :avocado: tags=device:virtio-vga > > > + """ > > > + kernel_command_line = ( > > > + self.KERNEL_COMMON_COMMAND_LINE + "console=ttyS0 > rdinit=/bin/bash" > > > + ) > > > + # FIXME: should check presence of virtio, virgl etc > > > This little nugget really must be fixed. > > The observed behaviour is an indefinite hang in avocado, waiting for qemu, > which is in > zombie state. A manual kill -INT to the parent wakes it up like so: > > (159/184) > tests/avocado/virtio-gpu.py:VirtioGPUx86.test_virtio_vga_virgl: CANCEL: > VirGL > not enabled? (1264.25 s) > > Could you describe how to reproduce? I naively --disable-virglrenderer and I get: $ tests/venv/bin/avocado run tests/avocado/virtio-gpu.py Fetching asset from tests/avocado/virtio-gpu.py:VirtioGPUx86.test_virtio_vga_virgl Fetching asset from tests/avocado/virtio-gpu.py:VirtioGPUx86.test_virtio_vga_virgl Fetching asset from tests/avocado/virtio-gpu.py:VirtioGPUx86.test_vhost_user_vga_virgl Fetching asset from tests/avocado/virtio-gpu.py:VirtioGPUx86.test_vhost_user_vga_virgl JOB ID : d9c5b65777777564d1d926fdfb58deaf0e967d15 JOB LOG : /home/elmarco/avocado/job-results/job-2022-06-27T12.56-d9c5b65/job.log (1/2) tests/avocado/virtio-gpu.py:VirtioGPUx86.test_virtio_vga_virgl: CANCEL: VirGL not enabled? (0.08 s) (2/2) tests/avocado/virtio-gpu.py:VirtioGPUx86.test_vhost_user_vga_virgl: CANCEL: Could not find vhost-user-gpu (0.02 s) RESULTS : PASS 0 | ERROR 0 | FAIL 0 | SKIP 0 | WARN 0 | INTERRUPT 0 | CANCEL 2 JOB TIME : 0.56 s -- Marc-André Lureau
