From: "Nguyen, Brian" <brian3.nguyen@intel.com>
To: <intel-xe@lists.freedesktop.org>
Subject: Re: ✗ Xe.CI.FULL: failure for Page Reclamation Fixes (rev5)
Date: Wed, 11 Mar 2026 11:14:37 -0700 [thread overview]
Message-ID: <47c69b98-f6ec-4fae-a6e7-16fe7fdd1ef2@intel.com> (raw)
In-Reply-To: <177294802851.330502.4629589411295974014@a3b018990fe9>
[-- Attachment #1: Type: text/plain, Size: 1597 bytes --]
On 3/7/2026 9:33 PM, Patchwork wrote:
> Project List - Patchwork *Patch Details*
> *Series:* Page Reclamation Fixes (rev5)
> *URL:* https://patchwork.freedesktop.org/series/162258/
> *State:* failure
> *Details:*
> https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-162258v5/index.html
>
>
> CI Bug Log - changes from
> xe-4675-fce8d7fb2107068c269b868d51aba5f9cf85998a_FULL ->
> xe-pw-162258v5_FULL
>
>
> Summary
>
> *FAILURE*
>
> Serious unknown changes coming with xe-pw-162258v5_FULL absolutely
> need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in xe-pw-162258v5_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-162258v5_FULL:
>
>
> IGT changes
>
>
> Possible regressions
>
> * igt@kms_cursor_crc@cursor-dpms@pipe-a-dp-2:
> o shard-bmg: PASS
> <https://intel-gfx-ci.01.org/tree/intel-xe/xe-4675-fce8d7fb2107068c269b868d51aba5f9cf85998a/shard-bmg-5/igt@kms_cursor_crc@cursor-dpms@pipe-a-dp-2.html>
> -> INCOMPLETE
> <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-162258v5/shard-bmg-1/igt@kms_cursor_crc@cursor-dpms@pipe-a-dp-2.html>
> +1 other test incomplete
>
Failure is unrelated to the patch series changes. CI looks healthy for
this patch series.
[-- Attachment #2: Type: text/html, Size: 3021 bytes --]
next prev parent reply other threads:[~2026-03-11 18:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 17:15 [PATCH v4 0/3] Page Reclamation Fixes Brian Nguyen
2026-03-05 17:15 ` [PATCH v4 1/3] drm/xe: Skip over non leaf pte for PRL generation Brian Nguyen
2026-03-05 17:15 ` [PATCH v4 2/3] drm/xe: Move page reclaim done_handler to own func Brian Nguyen
2026-03-05 17:15 ` [PATCH v4 3/3] drm/xe: Skip adding PRL entry to NULL VMA Brian Nguyen
2026-03-06 15:33 ` ✓ CI.KUnit: success for Page Reclamation Fixes (rev4) Patchwork
2026-03-06 16:36 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-03-07 1:53 ` ✓ CI.KUnit: success for Page Reclamation Fixes (rev5) Patchwork
2026-03-07 2:46 ` ✓ Xe.CI.BAT: " Patchwork
2026-03-08 5:33 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-03-11 18:14 ` Nguyen, Brian [this message]
2026-03-16 16:44 ` Matt Roper
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=47c69b98-f6ec-4fae-a6e7-16fe7fdd1ef2@intel.com \
--to=brian3.nguyen@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