[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <92467afc-cd50-41aa-a3a5-481c9da30a4c@collabora.com>
Date: Fri, 24 Nov 2023 13:16:26 +0530
From: Vignesh Raman <vignesh.raman@...labora.com>
To: Daniel Stone <daniel@...ishbar.org>
Cc: helen.koike@...labora.com, airlied@...il.com, daniel@...ll.ch,
daniels@...labora.com, emma@...olt.net,
gustavo.padovan@...labora.com, linux-arm-msm@...r.kernel.org,
guilherme.gallo@...labora.com, sergi.blanch.torne@...labora.com,
linux-kernel@...r.kernel.org, dri-devel@...ts.freedesktop.org,
virtualization@...ts.linux-foundation.org,
david.heidelberg@...labora.com, linux-mediatek@...ts.infradead.org
Subject: Re: [PATCH v5 9/9] drm: ci: Update xfails
Hi Daniel,
On 19/10/23 13:55, Daniel Stone wrote:
>
> By the time we get this error, it indicates that there was previously
> memory corruption, but it is only being noticed at a later point. The
> skip lists here are way too big - stuff like drm_read is common
> testing not affected by virtio at all - so we really need to isolate
> the test which is actually breaking things.
>
> The way to do this would be to use valgrind to detect where the memory
> corruption is. VirtIO can be run locally so this is something you can
> do on your machine.
Thank you for the hints and suggestions. This is now fixed in
igt-gpu-tools, and the patches are merged. I will uprev igt in drm-ci
and rerun the tests.
Also will drop the tests from virtio_gpu-none-skips.txt and send an
updated version.
Regards,
Vignesh
Powered by blists - more mailing lists