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 tests/intel/intel_sysfs_debugfs: Unify sysfs and debugfs testing (rev2)
Date: Tue, 1 Apr 2025 10:34:07 +0200 [thread overview]
Message-ID: <4339c705-a19e-417b-bb94-f562c63b7e85@linux.intel.com> (raw)
In-Reply-To: <174346529452.21412.6795674895879532025@e6b6f09ec485>
Dear I915,
On 4/1/2025 1:54 AM, Patchwork wrote:
> == Series Details ==
>
> Series: tests/intel/intel_sysfs_debugfs: Unify sysfs and debugfs testing (rev2)
> URL : https://patchwork.freedesktop.org/series/146940/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from XEIGT_8294_FULL -> XEIGTPW_12891_FULL
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with XEIGTPW_12891_FULL absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in XEIGTPW_12891_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 -> 4)
> ------------------------------
>
> No changes in participating hosts
>
> Possible new issues
> -------------------
>
> Here are the unknown changes that may have been introduced in XEIGTPW_12891_FULL:
>
> ### IGT changes ###
>
> #### Possible regressions ####
>
> * igt@kms_plane_multiple@2x-tiling-yf:
> - shard-bmg: NOTRUN -> [SKIP][1]
> [1]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_12891/shard-bmg-3/igt@kms_plane_multiple@2x-tiling-yf.html
>
> * igt@kms_pm_rpm@modeset-stress-extra-wait:
> - shard-dg2-set2: NOTRUN -> [INCOMPLETE][2] +4 other tests incomplete
> [2]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_12891/shard-dg2-432/igt@kms_pm_rpm@modeset-stress-extra-wait.html
>
> * igt@kms_pm_rpm@universal-planes-dpms@plane-50:
> - shard-lnl: NOTRUN -> [INCOMPLETE][3] +1 other test incomplete
> [3]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_12891/shard-lnl-7/igt@kms_pm_rpm@universal-planes-dpms@plane-50.html
>
> * igt@kms_psr@fbc-psr2-cursor-render@edp-1:
> - shard-lnl: NOTRUN -> [SKIP][4] +12 other tests skip
> [4]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_12891/shard-lnl-3/igt@kms_psr@fbc-psr2-cursor-render@edp-1.html
>
>
> #### Suppressed ####
>
> The following results come from untrusted machines, tests, or statuses.
> They do not affect the overall result.
>
> * {igt@xe_eu_stall@invalid-event-report-count}:
> - shard-dg2-set2: NOTRUN -> [SKIP][5]
> [5]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_12891/shard-dg2-432/igt@xe_eu_stall@invalid-event-report-count.html
> - shard-adlp: NOTRUN -> [SKIP][6] +1 other test skip
> [6]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_12891/shard-adlp-2/igt@xe_eu_stall@invalid-event-report-count.html
These are unrelated to my change.
Thank you,
Peter
next prev parent reply other threads:[~2025-04-01 8:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 18:05 [PATCH v4 i-g-t 0/1] tests/intel/intel_sysfs_debugfs: Unify sysfs and debugfs testing Peter Senna Tschudin
2025-03-31 18:05 ` [PATCH v4 i-g-t 1/1] tests/intel/intel_sysfs_debugfs " Peter Senna Tschudin
2025-03-31 20:30 ` ✗ i915.CI.BAT: failure for tests/intel/intel_sysfs_debugfs: Unify sysfs and debugfs testing (rev2) Patchwork
2025-04-01 8:32 ` Peter Senna Tschudin
2025-04-01 11:23 ` Ravali, JupallyX
2025-03-31 20:45 ` ✓ Xe.CI.BAT: success " Patchwork
2025-03-31 21:56 ` [PATCH v4 i-g-t 0/1] tests/intel/intel_sysfs_debugfs: Unify sysfs and debugfs testing Rodrigo Vivi
2025-03-31 23:54 ` ✗ Xe.CI.Full: failure for tests/intel/intel_sysfs_debugfs: Unify sysfs and debugfs testing (rev2) Patchwork
2025-04-01 8:34 ` Peter Senna Tschudin [this message]
2025-04-01 11:21 ` ✓ i915.CI.BAT: success " Patchwork
2025-04-01 15:01 ` ✗ i915.CI.Full: failure " Patchwork
2025-04-06 22:05 ` ✗ Xe.CI.Full: " 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=4339c705-a19e-417b-bb94-f562c63b7e85@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