Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Sousa <gustavo.sousa@intel.com>
To: Patchwork <patchwork@emeril.freedesktop.org>,
	<intel-xe@lists.freedesktop.org>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: ✗ Xe.CI.Full: failure for drm/i915/dmc_wl: Do not check for DMC payload
Date: Wed, 5 Feb 2025 08:57:36 -0300	[thread overview]
Message-ID: <173875665602.111435.9816988754782654416@intel.com> (raw)
In-Reply-To: <173778013918.99963.4420744416382785770@b555e5b46a47>

Quoting Patchwork (2025-01-25 01:42:19-03:00)
>== Series Details ==
>
>Series: drm/i915/dmc_wl: Do not check for DMC payload
>URL   : https://patchwork.freedesktop.org/series/143950/
>State : failure
>
>== Summary ==
>
>CI Bug Log - changes from xe-2549-b36df02c99e3246ba2a90e951c71797327374db7_full -> xe-pw-143950v1_full
>====================================================
>
>Summary
>-------
>
>  **FAILURE**
>
>  Serious unknown changes coming with xe-pw-143950v1_full absolutely need to be
>  verified manually.
>  
>  If you think the reported changes have nothing to do with the changes
>  introduced in xe-pw-143950v1_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 xe-pw-143950v1_full:
>
>### IGT changes ###
>
>#### Possible regressions ####
>
>  * igt@kms_plane_scaling@intel-max-src-size@pipe-a-dp-2:
>    - shard-dg2-set2:     NOTRUN -> [DMESG-WARN][1] +1 other test dmesg-warn
>   [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143950v1/shard-dg2-432/igt@kms_plane_scaling@intel-max-src-size@pipe-a-dp-2.html

This maps to https://gitlab.freedesktop.org/drm/xe/kernel/issues/4212 .

>
>  * igt@xe_pm@s2idle-basic-exec:
>    - shard-adlp:         [PASS][2] -> [DMESG-WARN][3] +4 other tests dmesg-warn
>   [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2549-b36df02c99e3246ba2a90e951c71797327374db7/shard-adlp-2/igt@xe_pm@s2idle-basic-exec.html
>   [3]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143950v1/shard-adlp-2/igt@xe_pm@s2idle-basic-exec.html

This maps to
https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/4391 .

>
>  * igt@xe_pm_residency@gt-c6-freeze:
>    - shard-dg2-set2:     [PASS][4] -> [ABORT][5] +1 other test abort
>   [4]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2549-b36df02c99e3246ba2a90e951c71797327374db7/shard-dg2-436/igt@xe_pm_residency@gt-c6-freeze.html
>   [5]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143950v1/shard-dg2-432/igt@xe_pm_residency@gt-c6-freeze.html

Aborted due to network issues between runner and the test machine.

--
Gustavo Sousa

  reply	other threads:[~2025-02-05 11:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-24 19:12 [PATCH] drm/i915/dmc_wl: Do not check for DMC payload Gustavo Sousa
2025-01-24 21:36 ` ✓ CI.Patch_applied: success for " Patchwork
2025-01-24 21:36 ` ✓ CI.checkpatch: " Patchwork
2025-01-24 21:37 ` ✓ CI.KUnit: " Patchwork
2025-01-24 21:54 ` ✓ CI.Build: " Patchwork
2025-01-24 21:57 ` ✓ CI.Hooks: " Patchwork
2025-01-24 22:00 ` ✓ CI.checksparse: " Patchwork
2025-01-24 22:34 ` ✓ Xe.CI.BAT: " Patchwork
2025-01-25  4:42 ` ✗ Xe.CI.Full: failure " Patchwork
2025-02-05 11:57   ` Gustavo Sousa [this message]
2025-01-30  9:41 ` [PATCH] " Luca Coelho
2025-01-30 14:18 ` Krzysztof Karas
2025-01-31 20:16   ` Gustavo Sousa
2025-01-31 23:49     ` Lucas De Marchi
2025-02-03 11:44       ` Gustavo Sousa
2025-02-05  9:07         ` Krzysztof Karas
2025-02-05 14:18 ` Gustavo Sousa

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=173875665602.111435.9816988754782654416@intel.com \
    --to=gustavo.sousa@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=patchwork@emeril.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