Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Senna Tschudin <peter.senna@linux.intel.com>
To: igt-dev@lists.freedesktop.org, I915-ci-infra@lists.freedesktop.org
Subject: Re: ✗ i915.CI.Full: failure for Replace intel_sysfs_debugfs (rev2)
Date: Fri, 23 May 2025 09:53:48 +0200	[thread overview]
Message-ID: <8099065e-f9d3-40fb-b46d-5d2174e46930@linux.intel.com> (raw)
In-Reply-To: <174793586182.14856.1031754515169725717@1538d3639d33>

Dear I915,

On 5/22/2025 7:44 PM, 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 IGT_8375_full -> IGTPW_13170_full
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with IGTPW_13170_full absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in IGTPW_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.
> 
>   External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_13170/index.html
> 
> Participating hosts (11 -> 10)
> ------------------------------
> 
>   Missing    (1): shard-dg2-set2 
> 
> Possible new issues
> -------------------
> 
>   Here are the unknown changes that may have been introduced in IGTPW_13170_full:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####
> 
>   * igt@gem_eio@kms:
>     - shard-snb:          [PASS][1] -> [INCOMPLETE][2]
>    [1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_8375/shard-snb5/igt@gem_eio@kms.html
>    [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_13170/shard-snb6/igt@gem_eio@kms.html
> 
>   * igt@kms_plane@plane-panning-bottom-right-suspend@pipe-a:
>     - shard-rkl:          NOTRUN -> [INCOMPLETE][3] +1 other test incomplete
>    [3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_13170/shard-rkl-3/igt@kms_plane@plane-panning-bottom-right-suspend@pipe-a.html
> 
>   
> #### Warnings ####
> 
>   * igt@i915_suspend@basic-s3-without-i915:
>     - shard-tglu:         [INCOMPLETE][4] ([i915#4817] / [i915#7443]) -> [INCOMPLETE][5]
>    [4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_8375/shard-tglu-5/igt@i915_suspend@basic-s3-without-i915.html
>    [5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_13170/shard-tglu-4/igt@i915_suspend@basic-s3-without-i915.html
> 

These are unrelated to my change. Please fix.

Thank you,

Peter

  reply	other threads:[~2025-05-23  7:53 UTC|newest]

Thread overview: 15+ 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 [this message]
2025-05-23  3:40 ` ✗ Xe.CI.Full: " Patchwork
2025-05-23  7:52   ` Peter Senna Tschudin
  -- strict thread matches above, loose matches on Subject: below --
2025-06-16  7:42 [PATCH v3 resend i-g-t 0/6] Replace intel_sysfs_debugfs Peter Senna Tschudin
2025-07-04  4:29 ` ✗ i915.CI.Full: failure for Replace intel_sysfs_debugfs (rev2) 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=8099065e-f9d3-40fb-b46d-5d2174e46930@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