public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: intel-gfx@lists.freedesktop.org, I915-ci-infra@lists.freedesktop.org
Subject: Re: ✗ i915.CI.BAT: failure for Replace the dmabuf custom test framework with kunit
Date: Sun, 1 Mar 2026 16:03:34 -0400	[thread overview]
Message-ID: <20260301200334.GS5933@nvidia.com> (raw)
In-Reply-To: <177239473964.301330.2782864717131838844@a3b018990fe9>

On Sun, Mar 01, 2026 at 07:52:19PM +0000, Patchwork wrote:
>    Series:  Replace the dmabuf custom test framework with kunit
>    URL:     https://patchwork.freedesktop.org/series/162387/
>    State:   failure
>    Details: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_162387v1/index.ht ml

>    If you think the reported changes have nothing to do with the changes
>    introduced in Patchwork_162387v1, please notify your bug team
>    (I915-ci-infra@lists.freedesktop.org) to allow them
>    to document this new failure mode, which will reduce false positives in
>    CI.
> 
>    External URL:
>    https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_162387v1/index.html
 
> Possible new issues
> 
>    Here are the unknown changes that may have been introduced in
>    Patchwork_162387v1:
> 
>   IGT changes
> 
>     Possible regressions
> 
>      * igt@dmabuf@all-tests:
>           + fi-rkl-11600: [3]PASS -> [4]SKIP
[..]

This looks to be because the way to launch these DMABUF tests has
changed to kunit instead of the manual selftest. The test harness will
need an update once this is merged.

Jason

  reply	other threads:[~2026-03-01 20:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-01 18:57 [PATCH 0/5] Replace the dmabuf custom test framework with kunit Jason Gunthorpe
2026-03-01 18:57 ` [PATCH 1/5] dma-buf: Change st-dma-resv.c to use kunit Jason Gunthorpe
2026-03-01 18:57 ` [PATCH 2/5] dma-buf: Change st-dma-fence.c " Jason Gunthorpe
2026-03-01 18:57 ` [PATCH 3/5] dma-buf: Change st-dma-fence-unwrap.c " Jason Gunthorpe
2026-03-01 18:57 ` [PATCH 4/5] dma-buf: Change st-dma-fence-chain.c " Jason Gunthorpe
2026-03-01 18:57 ` [PATCH 5/5] dma-buf: Remove the old selftest Jason Gunthorpe
2026-03-01 19:52 ` ✗ i915.CI.BAT: failure for Replace the dmabuf custom test framework with kunit Patchwork
2026-03-01 20:03   ` Jason Gunthorpe [this message]
2026-03-02 11:43 ` [PATCH 0/5] " Christian König
2026-03-02 13:01   ` Jason Gunthorpe
2026-03-02 13:58     ` Christian König
2026-04-07 12:35       ` Jason Gunthorpe

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=20260301200334.GS5933@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=I915-ci-infra@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.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