Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Summers, Stuart" <stuart.summers@intel.com>
To: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re:  Xe.CI.BAT: failure for Add test coverage for multi queue reset (rev2)
Date: Tue, 28 Apr 2026 21:13:29 +0000	[thread overview]
Message-ID: <0cc019831ddbdff4d8055e0dd42095691ab7b705.camel@intel.com> (raw)
In-Reply-To: <177734317871.16746.4953414507810050609@5ab824fced77>

On Tue, 2026-04-28 at 02:26 +0000, Patchwork wrote:
> Patch Details
> Series: Add test coverage for multi queue reset (rev2) URL:
> https://patchwork.freedesktop.org/series/164653/ State: failure
> Details:
> https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_15066/index.html 
> CI Bug Log - changes from XEIGT_8874_BAT ->
> XEIGTPW_15066_BATSummaryFAILURE
> Serious unknown changes coming with XEIGTPW_15066_BAT absolutely need
> to be
>  verified manually.
> If you think the reported changes have nothing to do with the changes
>  introduced in XEIGTPW_15066_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 (13 -> 13)No changes in participating hosts
> Possible new issuesHere are the unknown changes that may have been
> introduced in XEIGTPW_15066_BAT:
> IGT changesPossible regressions * igt@xe_waitfence@reltime:bat-atsm-
> 2: PASS -> FAIL

This is in an unrelated test and I haven't made any changes here that
would impact atsm or the libraries associated with this test.

Thanks,
Stuart

> Build changes * IGT: IGT_8874 -> IGTPW_15066
>  * Linux: xe-4940-b6f6b69b2dffa9ad1c43b2149786b4630d41acbf -> xe-
> 4944-aea2c496abcf55b647c14fe720bfc4ea555aac6a
> IGTPW_15066: 6194ba6711d4d4f06685e11ccd8a4f25a7224ed9 @
> https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
>  IGT_8874: 4568b2c141ab630c34f8eb2b9afab8cbf8f3ce9e @
> https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
>  xe-4940-b6f6b69b2dffa9ad1c43b2149786b4630d41acbf:
> b6f6b69b2dffa9ad1c43b2149786b4630d41acbf
>  xe-4944-aea2c496abcf55b647c14fe720bfc4ea555aac6a:
> aea2c496abcf55b647c14fe720bfc4ea555aac6a


  reply	other threads:[~2026-04-28 21:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-27 21:20 [PATCH i-g-t 0/4] Add test coverage for multi queue reset Stuart Summers
2026-04-27 21:20 ` [PATCH i-g-t 1/4] tests/intel/xe_exec_reset: Remove CANCEL logic for CM variants Stuart Summers
2026-04-27 21:20 ` [PATCH i-g-t 2/4] tests/intel/xe_exec_reset: Add a comment about return for syncobj wait Stuart Summers
2026-04-27 21:20 ` [PATCH i-g-t 3/4] tests/intel/xe_exec_reset: Add checks for hanging queue wait_ufence return Stuart Summers
2026-04-27 21:20 ` [PATCH i-g-t 4/4] tests/intel/xe_exec_reset: Add multi queue subtests Stuart Summers
2026-04-28  1:52 ` ✓ i915.CI.BAT: success for Add test coverage for multi queue reset (rev2) Patchwork
2026-04-28  2:26 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-04-28 21:13   ` Summers, Stuart [this message]
2026-04-28  9:38 ` ✓ i915.CI.Full: success " Patchwork
2026-04-28 10:36 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-04-28 21:12   ` Summers, Stuart

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=0cc019831ddbdff4d8055e0dd42095691ab7b705.camel@intel.com \
    --to=stuart.summers@intel.com \
    --cc=igt-dev@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