Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Vignesh Raman <vignesh.raman@collabora.com>
To: Daniel Stone <daniel@fooishbar.org>
Cc: helen.koike@collabora.com, airlied@gmail.com, daniel@ffwll.ch,
	daniels@collabora.com, emma@anholt.net,
	gustavo.padovan@collabora.com, linux-arm-msm@vger.kernel.org,
	guilherme.gallo@collabora.com, sergi.blanch.torne@collabora.com,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	virtualization@lists.linux-foundation.org,
	david.heidelberg@collabora.com,
	linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v5 9/9] drm: ci: Update xfails
Date: Fri, 24 Nov 2023 13:16:26 +0530	[thread overview]
Message-ID: <92467afc-cd50-41aa-a3a5-481c9da30a4c@collabora.com> (raw)
In-Reply-To: <CAPj87rP=22Fw0h42U-p9fHd=6OHOu9Lj9kbpVMQVqL9U6BRE1A@mail.gmail.com>

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


  reply	other threads:[~2023-11-24  7:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-19  7:06 [PATCH v5 0/9] drm: ci: fixes Vignesh Raman
2023-10-19  7:06 ` [PATCH v5 1/9] drm: ci: igt_runner: Remove todo Vignesh Raman
2023-10-19  7:06 ` [PATCH v5 2/9] drm: ci: Force db410c to host mode Vignesh Raman
2023-10-19  7:06 ` [PATCH v5 3/9] drm: ci: Enable regulator Vignesh Raman
2023-10-19  7:06 ` [PATCH v5 4/9] drm: ci: Enable new jobs Vignesh Raman
2023-10-19  7:06 ` [PATCH v5 5/9] drm: ci: Use scripts/config to enable/disable configs Vignesh Raman
2023-10-19  7:06 ` [PATCH v5 6/9] drm: ci: mediatek: Set IGT_FORCE_DRIVER for mt8173 Vignesh Raman
2023-10-19  7:06 ` [PATCH v5 7/9] drm: ci: virtio: Make artifacts available Vignesh Raman
2023-10-19  7:06 ` [PATCH v5 8/9] drm: ci: Add pipeline url to fails and flakes files Vignesh Raman
2023-10-19  7:06 ` [PATCH v5 9/9] drm: ci: Update xfails Vignesh Raman
2023-10-19  8:20   ` Maxime Ripard
2023-10-19  8:25   ` Daniel Stone
2023-11-24  7:46     ` Vignesh Raman [this message]
2023-10-19 16:42   ` Helen Koike
2023-10-19 16:45     ` Helen Koike

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=92467afc-cd50-41aa-a3a5-481c9da30a4c@collabora.com \
    --to=vignesh.raman@collabora.com \
    --cc=airlied@gmail.com \
    --cc=daniel@ffwll.ch \
    --cc=daniel@fooishbar.org \
    --cc=daniels@collabora.com \
    --cc=david.heidelberg@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emma@anholt.net \
    --cc=guilherme.gallo@collabora.com \
    --cc=gustavo.padovan@collabora.com \
    --cc=helen.koike@collabora.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=sergi.blanch.torne@collabora.com \
    --cc=virtualization@lists.linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox