From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: <intel-xe@lists.freedesktop.org>
Subject: Re: ✗ Xe.CI.Full: failure for drm/xe/sysfs: Fix attributes registration on VFs (rev2)
Date: Wed, 17 Sep 2025 21:58:51 +0200 [thread overview]
Message-ID: <a9656a5e-e4c4-40dc-8538-2a84d86256a4@intel.com> (raw)
In-Reply-To: <175804873737.339046.13628726154183583298@1538d3639d33>
On 9/16/2025 8:52 PM, Patchwork wrote:
> *Patch Details*
> *Series:* drm/xe/sysfs: Fix attributes registration on VFs (rev2)
> *URL:* https://patchwork.freedesktop.org/series/154534/ <https://patchwork.freedesktop.org/series/154534/>
> *State:* failure
> *Details:* https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-154534v2/index.html <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-154534v2/index.html>
>
>
> CI Bug Log - changes from xe-3773-3ac9e8d2d7d36978999286401624d908e7d9ed32_FULL -> xe-pw-154534v2_FULL
>
>
> Summary
>
> *FAILURE*
>
> Serious unknown changes coming with xe-pw-154534v2_FULL absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in xe-pw-154534v2_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 (4 -> 4)
>
> No changes in participating hosts
>
>
> Possible new issues
>
> Here are the unknown changes that may have been introduced in xe-pw-154534v2_FULL:
>
>
> IGT changes
>
>
> Possible regressions
>
> * igt@xe_exec_compute_mode@many-execqueues-userptr-free:
> o shard-bmg: PASS <https://intel-gfx-ci.01.org/tree/intel-xe/xe-3773-3ac9e8d2d7d36978999286401624d908e7d9ed32/shard-bmg-3/igt@xe_exec_compute_mode@many-execqueues-userptr-free.html> -> FAIL <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-154534v2/shard-bmg-1/igt@xe_exec_compute_mode@many-execqueues-userptr-free.html>
(xe_exec_compute_mode:5752) xe/xe_ioctl-CRITICAL: Test assertion failure function xe_wait_ufence, file ../lib/xe/xe_ioctl.c:676:
(xe_exec_compute_mode:5752) xe/xe_ioctl-CRITICAL: Failed assertion: __xe_wait_ufence(fd, addr, value, exec_queue, &timeout) == 0
(xe_exec_compute_mode:5752) xe/xe_ioctl-CRITICAL: Last errno: 62, Timer expired
(xe_exec_compute_mode:5752) xe/xe_ioctl-CRITICAL: error: -62 != 0
Subtest many-execqueues-userptr-free failed.
unrelated as series is about sysfs only
prev parent reply other threads:[~2025-09-17 19:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 17:00 [PATCH v2 0/2] drm/xe/sysfs: Fix attributes registration on VFs Michal Wajdeczko
2025-09-16 17:00 ` [PATCH v2 1/2] drm/xe/vf: Don't expose sysfs attributes not applicable for VFs Michal Wajdeczko
2025-09-16 17:07 ` Lucas De Marchi
2025-09-16 17:00 ` [PATCH v2 2/2] drm/xe/sysfs: Simplify sysfs registration Michal Wajdeczko
2025-09-17 6:18 ` Raag Jadav
2025-09-17 10:24 ` Michal Wajdeczko
2025-09-17 10:52 ` Raag Jadav
2025-09-17 19:38 ` Lucas De Marchi
2025-09-18 8:14 ` Raag Jadav
2025-09-16 17:08 ` ✓ CI.KUnit: success for drm/xe/sysfs: Fix attributes registration on VFs (rev2) Patchwork
2025-09-16 17:54 ` ✓ Xe.CI.BAT: " Patchwork
2025-09-16 18:52 ` ✗ Xe.CI.Full: failure " Patchwork
2025-09-17 19:58 ` 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=a9656a5e-e4c4-40dc-8538-2a84d86256a4@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