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: ✗ Fi.CI.IGT: failure for tests/intel/xe_module_load: Handling of snd_hda_intel
Date: Mon, 14 Oct 2024 07:22:42 +0200	[thread overview]
Message-ID: <9225a1c3-e27f-4d19-9545-e7501b2b22d3@linux.intel.com> (raw)
In-Reply-To: <172867115948.1241715.10112439750607543080@2413ebb6fbb6>

Dear I915,

On 11.10.2024 20:25, Patchwork wrote:
> == Series Details ==
> 
> Series: tests/intel/xe_module_load: Handling of snd_hda_intel
> URL   : https://patchwork.freedesktop.org/series/139838/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from CI_DRM_15513_full -> IGTPW_11897_full
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with IGTPW_11897_full absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in IGTPW_11897_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_11897/index.html
> 
> Participating hosts (8 -> 8)
> ------------------------------
> 
>   Additional (1): shard-glk-0 
>   Missing    (1): shard-glk 
> 
> Possible new issues
> -------------------
> 
>   Here are the unknown changes that may have been introduced in IGTPW_11897_full:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####
> 
>   * igt@gem_exec_balancer@nop:
>     - shard-mtlp:         [PASS][1] -> [DMESG-WARN][2]
>    [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15513/shard-mtlp-7/igt@gem_exec_balancer@nop.html
>    [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_11897/shard-mtlp-7/igt@gem_exec_balancer@nop.html
> 
>   * igt@gem_exercise_blt@fast-copy:
>     - shard-dg1:          [PASS][3] -> [INCOMPLETE][4]
>    [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15513/shard-dg1-18/igt@gem_exercise_blt@fast-copy.html
>    [4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_11897/shard-dg1-15/igt@gem_exercise_blt@fast-copy.html
> 
>   * igt@i915_pm_freq_api@freq-suspend@gt0:
>     - shard-dg2:          [PASS][5] -> [INCOMPLETE][6] +1 other test incomplete
>    [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15513/shard-dg2-3/igt@i915_pm_freq_api@freq-suspend@gt0.html
>    [6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_11897/shard-dg2-7/igt@i915_pm_freq_api@freq-suspend@gt0.html
> 
>   * igt@kms_flip@flip-vs-suspend-interruptible:
>     - shard-snb:          [PASS][7] -> [DMESG-WARN][8] +1 other test dmesg-warn
>    [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15513/shard-snb7/igt@kms_flip@flip-vs-suspend-interruptible.html
>    [8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_11897/shard-snb1/igt@kms_flip@flip-vs-suspend-interruptible.html
> 
>   * igt@kms_plane@pixel-format-source-clamping:
>     - shard-tglu:         [PASS][9] -> [ABORT][10] +1 other test abort
>    [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15513/shard-tglu-3/igt@kms_plane@pixel-format-source-clamping.html
>    [10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_11897/shard-tglu-4/igt@kms_plane@pixel-format-source-clamping.html
> 
>   * igt@kms_psr2_sf@psr2-overlay-plane-update-continuous-sf@pipe-a-edp-1:
>     - shard-mtlp:         [PASS][11] -> [FAIL][12] +1 other test fail
>    [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15513/shard-mtlp-4/igt@kms_psr2_sf@psr2-overlay-plane-update-continuous-sf@pipe-a-edp-1.html
>    [12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_11897/shard-mtlp-3/igt@kms_psr2_sf@psr2-overlay-plane-update-continuous-sf@pipe-a-edp-1.html

These are unrelated to my patch.

Thank you!


[...]

      reply	other threads:[~2024-10-14  5:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-10  9:42 [PATCH i-g-t] tests/intel/xe_module_load: Handling of snd_hda_intel Peter Senna Tschudin
2024-10-10 10:40 ` ✓ CI.xeBAT: success for " Patchwork
2024-10-10 10:55 ` ✓ Fi.CI.BAT: " Patchwork
2024-10-10 13:22 ` [PATCH i-g-t] " Lucas De Marchi
2024-10-11  0:06 ` ✗ CI.xeFULL: failure for " Patchwork
2024-10-11  5:17   ` Peter Senna Tschudin
2024-10-11 18:25 ` ✗ Fi.CI.IGT: " Patchwork
2024-10-14  5:22   ` 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=9225a1c3-e27f-4d19-9545-e7501b2b22d3@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