From: John Harrison <john.c.harrison@intel.com>
To: <intel-gfx@lists.freedesktop.org>
Subject: Re: ✗ Fi.CI.IGT: failure for drm/i915/guc: Enable PXP GuC autoteardown flow (rev4)
Date: Mon, 14 Oct 2024 12:55:39 -0700 [thread overview]
Message-ID: <11962af3-3271-411e-b0da-ee94ecbf508a@intel.com> (raw)
In-Reply-To: <172874727079.1244174.2391740947101715627@2413ebb6fbb6>
[-- Attachment #1: Type: text/plain, Size: 2124 bytes --]
On 10/12/2024 08:34, Patchwork wrote:
> Project List - Patchwork *Patch Details*
> *Series:* drm/i915/guc: Enable PXP GuC autoteardown flow (rev4)
> *URL:* https://patchwork.freedesktop.org/series/138337/
> *State:* failure
> *Details:*
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138337v4/index.html
>
>
> CI Bug Log - changes from CI_DRM_15519_full -> Patchwork_138337v4_full
>
>
> Summary
>
> *FAILURE*
>
> Serious unknown changes coming with Patchwork_138337v4_full absolutely
> need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_138337v4_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 -> 8)
>
> Missing (2): shard-dg2-set2 shard-glk-0
>
>
> Possible new issues
>
> Here are the unknown changes that may have been introduced in
> Patchwork_138337v4_full:
>
>
> IGT changes
>
>
> Possible regressions
>
> * igt@gem_exec_balancer@nop:
> o shard-mtlp: PASS
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15519/shard-mtlp-3/igt@gem_exec_balancer@nop.html>
> -> DMESG-WARN
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138337v4/shard-mtlp-2/igt@gem_exec_balancer@nop.html>
>
Slow TLB invalidation processing (in both cases the completion message
was received a fraction of a second after the timeout fired). Not
related to PXP.
> *
>
>
> Warnings
>
> * igt@kms_psr2_sf@fbc-pr-overlay-plane-move-continuous-sf:
> o shard-mtlp: SKIP
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15519/shard-mtlp-2/igt@kms_psr2_sf@fbc-pr-overlay-plane-move-continuous-sf.html>
> (i915#12316
> <https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/12316>)
> -> FAIL
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138337v4/shard-mtlp-3/igt@kms_psr2_sf@fbc-pr-overlay-plane-move-continuous-sf.html>
>
Unstable display test, not related to PXP.
John.
[-- Attachment #2: Type: text/html, Size: 3919 bytes --]
prev parent reply other threads:[~2024-10-14 19:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 17:40 [PATCH v2] drm/i915/guc: Enable PXP GuC autoteardown flow John.C.Harrison
2024-09-06 17:52 ` Teres Alexis, Alan Previn
2024-09-06 18:34 ` ✗ Fi.CI.SPARSE: warning for " Patchwork
2024-09-06 19:02 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-09-18 19:32 ` ✗ Fi.CI.BAT: failure for drm/i915/guc: Enable PXP GuC autoteardown flow (rev2) Patchwork
2024-10-14 19:51 ` John Harrison
2024-09-26 19:47 ` ✗ Fi.CI.SPARSE: warning for drm/i915/guc: Enable PXP GuC autoteardown flow (rev3) Patchwork
2024-09-26 20:04 ` ✓ Fi.CI.BAT: success " Patchwork
2024-09-27 1:54 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-10-14 19:52 ` John Harrison
2024-09-28 0:40 ` Patchwork
2024-10-11 21:08 ` ✗ Fi.CI.SPARSE: warning for drm/i915/guc: Enable PXP GuC autoteardown flow (rev4) Patchwork
2024-10-11 21:54 ` ✓ Fi.CI.BAT: success " Patchwork
2024-10-12 15:34 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-10-14 19:55 ` John Harrison [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=11962af3-3271-411e-b0da-ee94ecbf508a@intel.com \
--to=john.c.harrison@intel.com \
--cc=intel-gfx@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