From: Gustavo Sousa <gustavo.sousa@intel.com>
To: Patchwork <patchwork@emeril.freedesktop.org>,
<intel-gfx@lists.freedesktop.org>
Cc: <intel-gfx@lists.freedesktop.org>
Subject: Re: ✗ i915.CI.Full: failure for Improve type-safety on POWER_DOMAIN_*() macros (rev4)
Date: Fri, 28 Feb 2025 13:27:22 -0300 [thread overview]
Message-ID: <174076004277.17587.15727830706467067728@intel.com> (raw)
In-Reply-To: <174073738030.3170591.6736921341755944744@b555e5b46a47>
Quoting Patchwork (2025-02-28 07:09:40-03:00)
>== Series Details ==
>
>Series: Improve type-safety on POWER_DOMAIN_*() macros (rev4)
>URL : https://patchwork.freedesktop.org/series/144726/
>State : failure
>
>== Summary ==
>
>CI Bug Log - changes from CI_DRM_16198_full -> Patchwork_144726v4_full
>====================================================
>
>Summary
>-------
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_144726v4_full absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_144726v4_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 (10 -> 10)
>------------------------------
>
> No changes in participating hosts
>
>Possible new issues
>-------------------
>
> Here are the unknown changes that may have been introduced in Patchwork_144726v4_full:
>
>### IGT changes ###
>
>#### Possible regressions ####
>
> * igt@gem_exec_parallel@fds@bcs0:
> - shard-dg1: [PASS][1] -> [INCOMPLETE][2] +1 other test incomplete
> [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_16198/shard-dg1-16/igt@gem_exec_parallel@fds@bcs0.html
> [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_144726v4/shard-dg1-12/igt@gem_exec_parallel@fds@bcs0.html
If we look at
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_144726v4/shard-dg1-12/dmesg1.txt
, we can see that the dynamic subtest actually passed. So the INCOMPLETE
here is possibly a result of some sync failure in CI tooling.
>
> * igt@kms_flip@plain-flip-ts-check-interruptible@c-hdmi-a1:
> - shard-tglu: [PASS][3] -> [FAIL][4] +2 other tests fail
> [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_16198/shard-tglu-4/igt@kms_flip@plain-flip-ts-check-interruptible@c-hdmi-a1.html
> [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_144726v4/shard-tglu-10/igt@kms_flip@plain-flip-ts-check-interruptible@c-hdmi-a1.html
>
> * igt@kms_flip@wf_vblank-ts-check@b-vga1:
> - shard-snb: [PASS][5] -> [FAIL][6]
> [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_16198/shard-snb1/igt@kms_flip@wf_vblank-ts-check@b-vga1.html
> [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_144726v4/shard-snb5/igt@kms_flip@wf_vblank-ts-check@b-vga1.html
Those two are possibly related to
https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13734 .
>
> * igt@perf_pmu@module-unload:
> - shard-tglu-1: NOTRUN -> [INCOMPLETE][7]
> [7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_144726v4/shard-tglu-1/igt@perf_pmu@module-unload.html
Possibly related to
https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13029 .
--
Gustavo Sousa
next prev parent reply other threads:[~2025-02-28 16:27 UTC|newest]
Thread overview: 9+ 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-28 0:12 ` ✗ Fi.CI.SPARSE: warning for Improve type-safety on POWER_DOMAIN_*() macros (rev4) Patchwork
2025-02-28 0:32 ` ✓ i915.CI.BAT: success " Patchwork
2025-02-28 10:09 ` ✗ i915.CI.Full: failure " Patchwork
2025-02-28 16:27 ` 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=174076004277.17587.15727830706467067728@intel.com \
--to=gustavo.sousa@intel.com \
--cc=intel-gfx@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