From: "Anirban, Sk" <sk.anirban@intel.com>
To: <intel-xe@lists.freedesktop.org>
Subject: Re: ✗ Xe.CI.FULL: failure for drm/xe/debugfs: Expose per-engine idle status (rev5)
Date: Tue, 15 Sep 2026 22:14:52 +0530 [thread overview]
Message-ID: <ae265075-0481-4a9d-8d50-cb750bcd0374@intel.com> (raw)
In-Reply-To: <178909114179.147924.17797398735215807849@61270ab9df2a>
[-- Attachment #1: Type: text/plain, Size: 1699 bytes --]
Hi,
These failures are not related to my changes. Could someone please
re-report?
Thanks.
Anirban
On 11-09-2026 07:15 am, Patchwork wrote:
> Project List - Patchwork *Patch Details*
> *Series:* drm/xe/debugfs: Expose per-engine idle status (rev5)
> *URL:* https://patchwork.freedesktop.org/series/168204/
> *State:* failure
> *Details:*
> https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-168204v5/index.html
>
>
> CI Bug Log - changes from
> xe-5723-de0b423cd4c2178272a2057ee6c7b05fbd4015a6_FULL ->
> xe-pw-168204v5_FULL
>
>
> Summary
>
> *FAILURE*
>
> Serious unknown changes coming with xe-pw-168204v5_FULL absolutely
> need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in xe-pw-168204v5_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-168204v5_FULL:
>
>
> IGT changes
>
>
> Possible regressions
>
> * igt@xe_exec_system_allocator@partial-atomic-middle-remap-no-cpu-fault:
>
> o shard-bmg: PASS
> <https://intel-gfx-ci.01.org/tree/intel-xe/xe-5723-de0b423cd4c2178272a2057ee6c7b05fbd4015a6/shard-bmg-10/igt@xe_exec_system_allocator@partial-atomic-middle-remap-no-cpu-fault.html>
> -> FAIL
> <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-168204v5/shard-bmg-8/igt@xe_exec_system_allocator@partial-atomic-middle-remap-no-cpu-fault.html>
>
>
> Known issues
>
[-- Attachment #2: Type: text/html, Size: 3158 bytes --]
prev parent reply other threads:[~2026-09-15 16:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 16:58 [PATCH v3] drm/xe/debugfs: Expose per-engine idle status Sk Anirban
2026-09-10 17:17 ` ✓ CI.KUnit: success for drm/xe/debugfs: Expose per-engine idle status (rev5) Patchwork
2026-09-10 17:31 ` [PATCH v3] drm/xe/debugfs: Expose per-engine idle status sashiko-bot
2026-09-10 18:25 ` ✓ Xe.CI.BAT: success for drm/xe/debugfs: Expose per-engine idle status (rev5) Patchwork
2026-09-11 1:45 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-09-15 16:44 ` Anirban, Sk [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=ae265075-0481-4a9d-8d50-cb750bcd0374@intel.com \
--to=sk.anirban@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.