From: Peter Senna Tschudin <peter.senna@linux.intel.com>
To: igt-dev@lists.freedesktop.org, I915-ci-infra@lists.freedesktop.org
Subject: Re: ✗ Xe.CI.Full: failure for Replace intel_sysfs_debugfs (rev2)
Date: Fri, 23 May 2025 09:52:46 +0200 [thread overview]
Message-ID: <7940fd09-2b6c-41a6-856d-5d75ec91880d@linux.intel.com> (raw)
In-Reply-To: <174797163358.16284.251730595330315343@1538d3639d33>
Dear I915,
On 5/23/2025 5:40 AM, Patchwork wrote:
> == Series Details ==
>
> Series: Replace intel_sysfs_debugfs (rev2)
> URL : https://patchwork.freedesktop.org/series/149023/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from XEIGT_8375_FULL -> XEIGTPW_13170_FULL
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with XEIGTPW_13170_FULL absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in XEIGTPW_13170_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_13170_FULL:
>
> ### IGT changes ###
>
> #### Possible regressions ####
>
> * igt@kms_plane@planar-pixel-format-settings:
> - shard-bmg: NOTRUN -> [FAIL][1]
> [1]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13170/shard-bmg-6/igt@kms_plane@planar-pixel-format-settings.html
>
> * igt@xe_exec_basic@multigpu-once-basic-defer-bind:
> - shard-dg2-set2: [PASS][2] -> [INCOMPLETE][3]
> [2]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8375/shard-dg2-434/igt@xe_exec_basic@multigpu-once-basic-defer-bind.html
> [3]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_13170/shard-dg2-433/igt@xe_exec_basic@multigpu-once-basic-defer-bind.html
These are unrelated to my change. Please fix.
Thank you,
Peter
prev parent reply other threads:[~2025-05-23 7:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 11:00 [PATCH i-g-t 0/5] Replace intel_sysfs_debugfs Peter Senna Tschudin
2025-05-22 11:00 ` [PATCH i-g-t 1/5] Remove tests/intel/intel_sysfs_debugfs Peter Senna Tschudin
2025-06-12 17:51 ` Kamil Konieczny
2025-05-22 11:00 ` [PATCH i-g-t 2/5] lib/igt_dir: Directory processing and flexible file handling Peter Senna Tschudin
2025-05-22 11:00 ` [PATCH i-g-t 3/5] Add tests: core_debugfs and core_debugfs_display_on_off Peter Senna Tschudin
2025-06-12 18:17 ` Kamil Konieczny
2025-05-22 11:00 ` [PATCH i-g-t 4/5] tests/core_sysfs: Add GPU-agnostic sysfs testing Peter Senna Tschudin
2025-05-22 11:00 ` [PATCH i-g-t 5/5] tests/intel/xe_debugfs: Add Xe-specific debugfs test Peter Senna Tschudin
2025-05-22 14:43 ` ✓ i915.CI.BAT: success for Replace intel_sysfs_debugfs (rev2) Patchwork
2025-05-22 14:51 ` ✓ Xe.CI.BAT: " Patchwork
2025-05-22 17:44 ` ✗ i915.CI.Full: failure " Patchwork
2025-05-23 7:53 ` Peter Senna Tschudin
2025-05-23 3:40 ` ✗ Xe.CI.Full: " Patchwork
2025-05-23 7:52 ` Peter Senna Tschudin [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=7940fd09-2b6c-41a6-856d-5d75ec91880d@linux.intel.com \
--to=peter.senna@linux.intel.com \
--cc=I915-ci-infra@lists.freedesktop.org \
--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