Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: intel-xe@lists.freedesktop.org
Subject: Re: ✗ Xe.CI.BAT: failure for drm/xe: Add a per-client debugfs file reporting bo NUMA node distribution (rev5)
Date: Thu, 19 Nov 2026 14:17:46 +0100	[thread overview]
Message-ID: <c7655943615f2018687a987d646e4173c457d7d8.camel@linux.intel.com> (raw)
In-Reply-To: <179502680832.46043.561995994803801529@9ac1b63fe3ea>

On Wed, 2026-11-18 at 18:33 +0000, Patchwork wrote:
> == Series Details ==
> 
> Series: drm/xe: Add a per-client debugfs file reporting bo NUMA node
> distribution (rev5)
> URL   : https://patchwork.freedesktop.org/series/177016/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from xe-6175-
> e7c60d65b141a5bd0916a4aecf0423496da8455c_BAT -> xe-pw-177016v5_BAT
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with xe-pw-177016v5_BAT absolutely
> need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the
> changes
>   introduced in xe-pw-177016v5_BAT, 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.
> 
>   
> 
> Participating hosts (15 -> 15)
> ------------------------------
> 
>   No changes in participating hosts
> 
> Possible new issues
> -------------------
> 
>   Here are the unknown changes that may have been introduced in xe-
> pw-177016v5_BAT:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####
> 
>   * igt@xe_multigpu_svm@mgpu-migration-prefetch:
>     - bat-bmg-3:          [PASS][1] -> [DMESG-WARN][2]
>    [1]:
> https://intel-gfx-ci.01.org/tree/intel-xe/xe-6175-e7c60d65b141a5bd0916a4aecf0423496da8455c/bat-bmg-3/igt@xe_multigpu_svm@mgpu-migration-prefetch.html
>    [2]:
> https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-177016v5/bat-bmg-3/igt@xe_multigpu_svm@mgpu-migration-prefetch.html
> 
>   

Unrelated.

> 
> 
> Build changes
> -------------
> 
>   * Linux: xe-6175-e7c60d65b141a5bd0916a4aecf0423496da8455c -> xe-pw-
> 177016v5
> 
>   IGT_9197: 9197
>   xe-6175-e7c60d65b141a5bd0916a4aecf0423496da8455c:
> e7c60d65b141a5bd0916a4aecf0423496da8455c
>   xe-pw-177016v5: 177016v5
> 
> == Logs ==
> 
> For more details see:
> https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-177016v5/index.html

  reply	other threads:[~2026-11-19 13:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-18 13:42 [PATCH v3] drm/xe: Add a per-client debugfs file reporting bo NUMA node distribution Thomas Hellström
2026-11-18 15:01 ` Thomas Hellström
2026-11-18 17:39 ` ✓ CI.KUnit: success for drm/xe: Add a per-client debugfs file reporting bo NUMA node distribution (rev5) Patchwork
2026-11-18 18:33 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-11-19 13:17   ` Thomas Hellström [this message]
2026-11-19 12:44 ` ✓ Xe.CI.FULL: success " Patchwork
2026-11-19 20:39 ` [PATCH v3] drm/xe: Add a per-client debugfs file reporting bo NUMA node distribution Andi Shyti

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=c7655943615f2018687a987d646e4173c457d7d8.camel@linux.intel.com \
    --to=thomas.hellstrom@linux.intel.com \
    --cc=intel-xe@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