Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Vivekanandan, Balasubramani" <balasubramani.vivekanandan@intel.com>
To: <intel-xe@lists.freedesktop.org>
Subject: Re: ✗ Xe.CI.FULL: failure for Refactor functions implementing the blt batch buffer (rev2)
Date: Tue, 12 May 2026 10:57:00 +0530	[thread overview]
Message-ID: <agK6JD-T5t41amFZ@bvivekan-mob1> (raw)
In-Reply-To: <177853137200.58917.1057195695448194023@5ab824fced77>

On 11.05.2026 20:29, Patchwork wrote:
> == Series Details ==
> 
> Series: Refactor functions implementing the blt batch buffer (rev2)
> URL   : https://patchwork.freedesktop.org/series/166104/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from xe-5041-f8ee23694aa6be213355905a78f79bb1b0861565_FULL -> xe-pw-166104v2_FULL
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with xe-pw-166104v2_FULL absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in xe-pw-166104v2_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-166104v2_FULL:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####
> 
>   * igt@xe_exec_reset@long-spin-reuse-many-preempt:
>     - shard-bmg:          [PASS][1] -> [FAIL][2]
>    [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-5041-f8ee23694aa6be213355905a78f79bb1b0861565/shard-bmg-2/igt@xe_exec_reset@long-spin-reuse-many-preempt.html
>    [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-166104v2/shard-bmg-4/igt@xe_exec_reset@long-spin-reuse-many-preempt.html
> 

Failure is not related to the patch. Same test is passing on rev1 - https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-166104v1/shard-bmg-2/igt@xe_exec_reset@long-spin-reuse-many-preempt.html.
rev2 is a non-functional change. So it is a random failure and not from
the patch.

Regards,
Bala


      reply	other threads:[~2026-05-12  5:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-11 12:37 [PATCH v2 0/3] Refactor functions implementing the blt batch buffer Balasubramani Vivekanandan
2026-05-11 12:37 ` [PATCH v2 1/3] drm/xe: Refactor emit_clear_main_copy Balasubramani Vivekanandan
2026-05-11 19:30   ` Matt Roper
2026-05-11 12:37 ` [PATCH v2 2/3] drm/xe: Refactor emit_clear_link_copy Balasubramani Vivekanandan
2026-05-11 19:34   ` Matt Roper
2026-05-11 12:37 ` [PATCH v2 3/3] drm/xe: Refactor emit_xy_fast_copy and emit_mem_copy functions Balasubramani Vivekanandan
2026-05-11 19:45   ` Matt Roper
2026-05-11 17:25 ` ✓ CI.KUnit: success for Refactor functions implementing the blt batch buffer (rev2) Patchwork
2026-05-11 18:16 ` ✓ Xe.CI.BAT: " Patchwork
2026-05-11 20:29 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-05-12  5:27   ` Vivekanandan, Balasubramani [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=agK6JD-T5t41amFZ@bvivekan-mob1 \
    --to=balasubramani.vivekanandan@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