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 Close sysfs and debugfs test gap between i915 and Xe
Date: Tue, 18 Mar 2025 13:36:06 +0100	[thread overview]
Message-ID: <9b59e883-8cba-431f-9120-c11126bed834@linux.intel.com> (raw)
In-Reply-To: <174230018303.48165.12984179128478197757@18a75f3d1eae>

Dear I915,

On 18.03.2025 13:16, Patchwork wrote:
> == Series Details ==
> 
> Series: Close sysfs and debugfs test gap between i915 and Xe
> URL   : https://patchwork.freedesktop.org/series/146433/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from IGT_8276_full -> IGTPW_12790_full
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with IGTPW_12790_full absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in IGTPW_12790_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_12790/index.html
> 
> Participating hosts (10 -> 9)
> ------------------------------
> 
>   Missing    (1): shard-glk-0 
> 
> Possible new issues
> -------------------
> 
>   Here are the unknown changes that may have been introduced in IGTPW_12790_full:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####
> 
>   * igt@kms_flip@blocking-wf_vblank@a-hdmi-a1:
>     - shard-tglu:         [PASS][1] -> [FAIL][2] +1 other test fail
>    [1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_8276/shard-tglu-2/igt@kms_flip@blocking-wf_vblank@a-hdmi-a1.html
>    [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12790/shard-tglu-9/igt@kms_flip@blocking-wf_vblank@a-hdmi-a1.html
> 
>   * igt@kms_flip@blocking-wf_vblank@a-hdmi-a2:
>     - shard-rkl:          NOTRUN -> [FAIL][3]
>    [3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12790/shard-rkl-3/igt@kms_flip@blocking-wf_vblank@a-hdmi-a2.html
> 
>   * igt@kms_flip@plain-flip-ts-check:
>     - shard-dg2:          [PASS][4] -> [FAIL][5] +3 other tests fail
>    [4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_8276/shard-dg2-6/igt@kms_flip@plain-flip-ts-check.html
>    [5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12790/shard-dg2-5/igt@kms_flip@plain-flip-ts-check.html
> 
>   * igt@kms_flip@plain-flip-ts-check@a-edp1:
>     - shard-mtlp:         [PASS][6] -> [FAIL][7] +1 other test fail
>    [6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_8276/shard-mtlp-3/igt@kms_flip@plain-flip-ts-check@a-edp1.html
>    [7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12790/shard-mtlp-7/igt@kms_flip@plain-flip-ts-check@a-edp1.html
> 
>   * igt@kms_flip@plain-flip-ts-check@b-vga1:
>     - shard-snb:          [PASS][8] -> [FAIL][9] +2 other tests fail
>    [8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_8276/shard-snb5/igt@kms_flip@plain-flip-ts-check@b-vga1.html
>    [9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12790/shard-snb4/igt@kms_flip@plain-flip-ts-check@b-vga1.html
> 
>   * igt@perf_pmu@busy-hang@bcs0:
>     - shard-mtlp:         [PASS][10] -> [DMESG-WARN][11]
>    [10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_8276/shard-mtlp-3/igt@perf_pmu@busy-hang@bcs0.html
>    [11]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12790/shard-mtlp-7/igt@perf_pmu@busy-hang@bcs0.html
> 
>   
> #### Warnings ####
> 
>   * igt@kms_flip@blocking-wf_vblank:
>     - shard-rkl:          [DMESG-WARN][12] ([i915#12964]) -> [FAIL][13]
>    [12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_8276/shard-rkl-7/igt@kms_flip@blocking-wf_vblank.html
>    [13]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12790/shard-rkl-3/igt@kms_flip@blocking-wf_vblank.html

These are unrelated to my change. Please fix and re-run.

Thank you,

Peter

  reply	other threads:[~2025-03-18 12:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-18  9:53 [PATCH i-g-t 0/1] Close sysfs and debugfs test gap between i915 and Xe Peter Senna Tschudin
2025-03-18  9:53 ` [PATCH i-g-t 1/1] tests/intel/xe_debugfs: Add tests to read all debugfs and sysfs files Peter Senna Tschudin
2025-03-18 15:56   ` Kamil Konieczny
2025-03-18 16:33     ` Peter Senna Tschudin
2025-03-18 21:41     ` Peter Senna Tschudin
2025-03-18 10:18 ` ✓ Xe.CI.BAT: success for Close sysfs and debugfs test gap between i915 and Xe Patchwork
2025-03-18 10:41 ` ✓ i915.CI.BAT: " Patchwork
2025-03-18 11:13 ` ✗ Xe.CI.Full: failure " Patchwork
2025-03-18 12:34   ` Peter Senna Tschudin
2025-03-18 12:16 ` ✗ i915.CI.Full: " Patchwork
2025-03-18 12:36   ` Peter Senna Tschudin [this message]
2025-03-19  8:55     ` Ravali, JupallyX

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=9b59e883-8cba-431f-9120-c11126bed834@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