Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: <intel-xe@lists.freedesktop.org>
Subject: Re: ✗ Xe.CI.FULL: failure for drm/xe/mmio: Small improvements (rev3)
Date: Tue, 23 Jun 2026 18:47:34 +0200	[thread overview]
Message-ID: <ca65bd5e-abe2-47f9-8bef-84b8abc864ca@intel.com> (raw)
In-Reply-To: <178217002636.103867.1310763212766721326@6beec6c84f66>



On 6/23/2026 1:13 AM, Patchwork wrote:
> *Patch Details*
> *Series:*	drm/xe/mmio: Small improvements (rev3)
> *URL:*	https://patchwork.freedesktop.org/series/167104/ <https://patchwork.freedesktop.org/series/167104/>
> *State:*	failure
> *Details:*	https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-167104v3/index.html <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-167104v3/index.html>
> 
> 
>   CI Bug Log - changes from xe-5286-6583dd200482a34bb17e5dc54551f91f53b79798_FULL -> xe-pw-167104v3_FULL
> 
> 
>     Summary
> 
> *WARNING*
> 
> Minor unknown changes coming with xe-pw-167104v3_FULL need to be verified
> manually.
> 
> If you think the reported changes have nothing to do with the changes
> introduced in xe-pw-167104v3_FULL, 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 (2 -> 2)
> 
> No changes in participating hosts
> 
> 
>     Possible new issues
> 
> Here are the unknown changes that may have been introduced in xe-pw-167104v3_FULL:
> 
> 
>       IGT changes
> 
> 
>         Warnings
> 
>   * igt@xe_sriov_flr@flr-vfs-parallel:
>       o shard-bmg: FAIL <https://intel-gfx-ci.01.org/tree/intel-xe/xe-5286-6583dd200482a34bb17e5dc54551f91f53b79798/shard-bmg-3/igt@xe_sriov_flr@flr-vfs-parallel.html> (Intel XE#6569 <https://gitlab.freedesktop.org/drm/xe/kernel/issues/6569>) -> INCOMPLETE <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-167104v3/shard-bmg-10/igt@xe_sriov_flr@flr-vfs-parallel.html>

no useful logs, likely just another CI glitch


      reply	other threads:[~2026-06-23 16:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-22 13:23 [PATCH v3 0/6] drm/xe/mmio: Small improvements Michal Wajdeczko
2026-06-22 13:23 ` [PATCH v3 1/6] drm/xe/mmio: Verify MMIO is available Michal Wajdeczko
2026-06-22 15:39   ` Matthew Auld
2026-06-22 13:23 ` [PATCH v3 2/6] drm/xe/mmio: Map MMIO BAR using managed version of pci_iomap Michal Wajdeczko
2026-06-22 15:43   ` Matthew Auld
2026-06-22 13:23 ` [PATCH v3 3/6] drm/xe/mmio: Add check for minimal BAR size Michal Wajdeczko
2026-06-22 15:43   ` Matthew Auld
2026-06-22 13:23 ` [PATCH v3 4/6] drm/xe/mmio: Drop tiles_fini action Michal Wajdeczko
2026-06-22 15:44   ` Matthew Auld
2026-06-22 13:23 ` [PATCH v3 5/6] drm/xe/mmio: Check MMIO BAR size when initializing tiles Michal Wajdeczko
2026-06-22 13:23 ` [PATCH v3 6/6] drm/xe/mmio: Prefer tile-based WARN message Michal Wajdeczko
2026-06-23  9:13   ` Matthew Auld
2026-06-22 17:56 ` ✓ CI.KUnit: success for drm/xe/mmio: Small improvements (rev3) Patchwork
2026-06-22 18:52 ` ✓ Xe.CI.BAT: " Patchwork
2026-06-22 23:13 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-06-23 16:47   ` Michal Wajdeczko [this message]

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=ca65bd5e-abe2-47f9-8bef-84b8abc864ca@intel.com \
    --to=michal.wajdeczko@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