From: "Anirban, Sk" <sk.anirban@intel.com>
To: <igt-dev@lists.freedesktop.org>
Cc: <kamil.konieczny@intel.com>, Riana Tauro <riana.tauro@intel.com>,
<I915-ci-infra@lists.freedesktop.org>
Subject: Re: ✗ Xe.CI.Full: failure for tests/intel/xe_survivability: Add xe_survivability test (rev12)
Date: Thu, 6 Nov 2025 15:35:21 +0530 [thread overview]
Message-ID: <8d93b054-418c-4503-b361-059f9d1324c1@intel.com> (raw)
In-Reply-To: <176231443150.18967.10993927745487233097@10055242dc62>
[-- Attachment #1: Type: text/plain, Size: 2667 bytes --]
Hi,
These reported failures are not related to my changes.
Please do re-report.
Thanks,
Anirban
On 05-11-2025 09:17, Patchwork wrote:
> Project List - Patchwork *Patch Details*
> *Series:* tests/intel/xe_survivability: Add xe_survivability test
> (rev12)
> *URL:* https://patchwork.freedesktop.org/series/154342/
> *State:* failure
> *Details:*
> https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13987/index.html
>
>
> CI Bug Log - changes from XEIGT_8607_FULL -> XEIGTPW_13987_FULL
>
>
> Summary
>
> *FAILURE*
>
> Serious unknown changes coming with XEIGTPW_13987_FULL absolutely need
> to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in XEIGTPW_13987_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 -> 3)
>
> Missing (1): shard-adlp
>
>
> Possible new issues
>
> Here are the unknown changes that may have been introduced in
> XEIGTPW_13987_FULL:
>
>
> IGT changes
>
>
> Possible regressions
>
> *
>
> igt@kms_sharpness_filter@invalid-filter-with-scaler:
>
> o shard-bmg: NOTRUN -> SKIP
> <https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13987/shard-bmg-4/igt@kms_sharpness_filter@invalid-filter-with-scaler.html>
> *
>
> igt@kms_vrr@seamless-rr-switch-virtual@pipe-a-edp-1:
>
> o shard-lnl: PASS
> <https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8607/shard-lnl-2/igt@kms_vrr@seamless-rr-switch-virtual@pipe-a-edp-1.html>
> -> FAIL
> <https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13987/shard-lnl-8/igt@kms_vrr@seamless-rr-switch-virtual@pipe-a-edp-1.html>
> +1 other test fail
> *
>
> igt@xe_survivability@i2c-functionality (NEW):
>
> o shard-dg2-set2: NOTRUN -> SKIP
> <https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13987/shard-dg2-466/igt@xe_survivability@i2c-functionality.html>
> +1 other test skip
> o shard-lnl: NOTRUN -> SKIP
> <https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13987/shard-lnl-8/igt@xe_survivability@i2c-functionality.html>
> +1 other test skip
>
>
> New tests
>
> New tests have been introduced between XEIGT_8607_FULL and
> XEIGTPW_13987_FULL:
>
>
> New IGT tests (2)
>
> *
>
> igt@xe_survivability@i2c-functionality:
>
> o Statuses : 1 pass(s) 2 skip(s)
> o Exec time: [0.0, 0.02] s
> *
>
> igt@xe_survivability@runtime-survivability:
>
> o Statuses : 1 pass(s) 2 skip(s)
> o Exec time: [0.0, 2.32] s
>
>
> Known issues
>
[-- Attachment #2: Type: text/html, Size: 4561 bytes --]
next prev parent reply other threads:[~2025-11-06 10:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 9:52 [i-g-t, v10, 0/2] tests/intel/xe_survivability: Add xe_survivability test Sk Anirban
2025-11-04 9:52 ` [i-g-t, v10, 1/2] tests/intel/xe_survivability: Add new xe_survivability test for i2c adapter Sk Anirban
2025-11-04 9:52 ` [i-g-t, v10, 2/2] tests/intel/xe_survivability: Add new test runtime survivability Sk Anirban
2025-11-04 22:32 ` ✗ Xe.CI.BAT: failure for tests/intel/xe_survivability: Add xe_survivability test (rev12) Patchwork
2025-11-05 11:46 ` Anirban, Sk
2025-11-06 5:11 ` Anirban, Sk
2025-11-05 3:41 ` ✗ i915.CI.BAT: " Patchwork
2025-11-05 3:47 ` ✗ Xe.CI.Full: " Patchwork
2025-11-06 10:05 ` Anirban, Sk [this message]
2025-11-07 9:18 ` Ravali, JupallyX
2025-11-07 9:09 ` ✓ i915.CI.BAT: success " Patchwork
2025-11-08 0:08 ` ✗ i915.CI.Full: failure " Patchwork
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=8d93b054-418c-4503-b361-059f9d1324c1@intel.com \
--to=sk.anirban@intel.com \
--cc=I915-ci-infra@lists.freedesktop.org \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@intel.com \
--cc=riana.tauro@intel.com \
/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