Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Sousa <gustavo.sousa@intel.com>
To: <intel-xe@lists.freedesktop.org>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: ✗ Xe.CI.Full: failure for Improve type-safety on POWER_DOMAIN_*() macros (rev4)
Date: Fri, 28 Feb 2025 13:02:31 -0300	[thread overview]
Message-ID: <174075855176.17587.15136957201847826883@intel.com> (raw)
In-Reply-To: <174071787466.3042998.14533074930593599228@b555e5b46a47>

Quoting Patchwork (2025-02-28 01:44:34-03:00)
>== Series Details ==
>
>Series: Improve type-safety on POWER_DOMAIN_*() macros (rev4)
>URL   : https://patchwork.freedesktop.org/series/144727/
>State : failure
>
>== Summary ==
>
>CI Bug Log - changes from xe-2729-e03a2fbda18fa9e3df6fc7bb0c6359f0ccddf9d4_full -> xe-pw-144727v4_full
>====================================================
>
>Summary
>-------
>
>  **FAILURE**
>
>  Serious unknown changes coming with xe-pw-144727v4_full absolutely need to be
>  verified manually.
>  
>  If you think the reported changes have nothing to do with the changes
>  introduced in xe-pw-144727v4_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-144727v4_full:
>
>### IGT changes ###
>
>#### Possible regressions ####
>
>  * igt@kms_vblank@ts-continuation-modeset:
>    - shard-adlp:         [PASS][1] -> [DMESG-WARN][2] +1 other test dmesg-warn
>   [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2729-e03a2fbda18fa9e3df6fc7bb0c6359f0ccddf9d4/shard-adlp-1/igt@kms_vblank@ts-continuation-modeset.html
>   [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-144727v4/shard-adlp-1/igt@kms_vblank@ts-continuation-modeset.html

This is possibly related to
https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/4173 .

>
>  * igt@xe_compute_preempt@compute-preempt-many@engine-drm_xe_engine_class_compute:
>    - shard-lnl:          [PASS][3] -> [ABORT][4] +1 other test abort
>   [3]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2729-e03a2fbda18fa9e3df6fc7bb0c6359f0ccddf9d4/shard-lnl-7/igt@xe_compute_preempt@compute-preempt-many@engine-drm_xe_engine_class_compute.html
>   [4]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-144727v4/shard-lnl-3/igt@xe_compute_preempt@compute-preempt-many@engine-drm_xe_engine_class_compute.html


This is possibly related to
https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/4278 .

--
Gustavo Sousa

  reply	other threads:[~2025-02-28 16:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-27 21:09 [PATCH v3 0/2] Improve type-safety on POWER_DOMAIN_*() macros Gustavo Sousa
2025-02-27 21:09 ` [PATCH v3 1/2] drm/i915/display: Use explicit base values in " Gustavo Sousa
2025-02-27 21:09 ` [PATCH v3 2/2] drm/i915/display: Make POWER_DOMAIN_*() always result in enum intel_display_power_domain Gustavo Sousa
2025-02-27 21:12 ` [PATCH v3 0/2] Improve type-safety on POWER_DOMAIN_*() macros Gustavo Sousa
2025-02-27 23:23 ` ✓ CI.Patch_applied: success for Improve type-safety on POWER_DOMAIN_*() macros (rev4) Patchwork
2025-02-27 23:23 ` ✓ CI.checkpatch: " Patchwork
2025-02-27 23:25 ` ✓ CI.KUnit: " Patchwork
2025-02-27 23:41 ` ✓ CI.Build: " Patchwork
2025-02-27 23:44 ` ✓ CI.Hooks: " Patchwork
2025-02-27 23:45 ` ✓ CI.checksparse: " Patchwork
2025-02-28  0:04 ` ✓ Xe.CI.BAT: " Patchwork
2025-02-28  4:44 ` ✗ Xe.CI.Full: failure " Patchwork
2025-02-28 16:02   ` Gustavo Sousa [this message]
2025-02-28 16:48 ` [PATCH v3 0/2] Improve type-safety on POWER_DOMAIN_*() macros 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=174075855176.17587.15136957201847826883@intel.com \
    --to=gustavo.sousa@intel.com \
    --cc=intel-xe@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