public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Anirban, Sk" <sk.anirban@intel.com>
To: <igt-dev@lists.freedesktop.org>
Subject: Re: ✗ Xe.CI.FULL: failure for tests/intel/xe_pm_residency: ensure C6 GT before cpg-gt-toggle
Date: Wed, 8 Apr 2026 12:16:24 +0530	[thread overview]
Message-ID: <c6ac10c1-1200-4c98-99a5-cf81f5a30ba2@intel.com> (raw)
In-Reply-To: <177309599281.335140.2306016128870622116@a3b018990fe9>

[-- Attachment #1: Type: text/plain, Size: 2110 bytes --]

Hi,

These failures are not related to my changes. Could you please re-report?

Thanks,

Anirban

On 10-03-2026 04:09 am, Patchwork wrote:
> Project List - Patchwork *Patch Details*
> *Series:* 	tests/intel/xe_pm_residency: ensure C6 GT before cpg-gt-toggle
> *URL:* 	https://patchwork.freedesktop.org/series/162863/
> *State:* 	failure
> *Details:* 
> https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_14700/index.html
>
>
>   CI Bug Log - changes from XEIGT_8787_FULL -> XEIGTPW_14700_FULL
>
>
>     Summary
>
> *FAILURE*
>
> Serious unknown changes coming with XEIGTPW_14700_FULL absolutely need 
> to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in XEIGTPW_14700_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 
> XEIGTPW_14700_FULL:
>
>
>       IGT changes
>
>
>         Possible regressions
>
>  *
>
>     igt@kms_cursor_legacy@flip-vs-cursor-legacy:
>
>       o shard-bmg: PASS
>         <https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8787/shard-bmg-4/igt@kms_cursor_legacy@flip-vs-cursor-legacy.html>
>         -> FAIL
>         <https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_14700/shard-bmg-4/igt@kms_cursor_legacy@flip-vs-cursor-legacy.html>
>         +2 other tests fail
>  *
>
>     igt@xe_fault_injection@inject-fault-probe-function-xe_pm_init_early:
>
>       o shard-bmg: PASS
>         <https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8787/shard-bmg-5/igt@xe_fault_injection@inject-fault-probe-function-xe_pm_init_early.html>
>         -> ABORT
>         <https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_14700/shard-bmg-2/igt@xe_fault_injection@inject-fault-probe-function-xe_pm_init_early.html>
>         +1 other test abort
>
>
>     Known issues
>
> Here are the changes found in XEIGTPW_14700_FULL that come from known 
> issues:
>

[-- Attachment #2: Type: text/html, Size: 3698 bytes --]

  reply	other threads:[~2026-04-08  6:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-09 10:57 [PATCH] tests/intel/xe_pm_residency: ensure C6 GT before cpg-gt-toggle Sk Anirban
2026-03-09 18:14 ` ✓ Xe.CI.BAT: success for " Patchwork
2026-03-09 18:17 ` ✓ i915.CI.BAT: " Patchwork
2026-03-09 22:39 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-04-08  6:46   ` Anirban, Sk [this message]
2026-03-10  1:59 ` ✗ i915.CI.Full: " Patchwork
2026-04-02 10:50 ` [PATCH] " Poosa, Karthik

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=c6ac10c1-1200-4c98-99a5-cf81f5a30ba2@intel.com \
    --to=sk.anirban@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