From: Julia Filipchuk <julia.filipchuk@intel.com>
To: <intel-gfx@lists.freedesktop.org>
Subject: Re: ✗ i915.CI.Full: failure for drm/i915/guc: Test GuC v70.74.0 for MTL, DG2
Date: Wed, 26 Aug 2026 13:09:00 -0700 [thread overview]
Message-ID: <eeb32ece-43bf-4883-b19a-6d09c6a9ca4f@intel.com> (raw)
In-Reply-To: <178727968466.72177.15796035856403537495@61270ab9df2a>
On 8/20/2026 7:34 PM, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915/guc: Test GuC v70.74.0 for MTL, DG2
> URL : https://patchwork.freedesktop.org/series/172543/
> State : failure
>
...
>
> #### Possible regressions ####
>
> * igt@kms_ccs@missing-ccs-buffer-y-tiled-gen12-mc-ccs@pipe-c-hdmi-a-1:
> - shard-rkl: NOTRUN -> [ABORT][1]
> [1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_172543v1/shard-rkl-5/igt@kms_ccs@missing-ccs-buffer-y-tiled-gen12-mc-ccs@pipe-c-hdmi-a-1.html
>
> * igt@kms_cursor_legacy@cursora-vs-flipb-legacy:
> - shard-snb: [PASS][2] -> [INCOMPLETE][3]
> [2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_19025/shard-snb7/igt@kms_cursor_legacy@cursora-vs-flipb-legacy.html
> [3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_172543v1/shard-snb5/igt@kms_cursor_legacy@cursora-vs-flipb-legacy.html
>
> * igt@kms_cursor_legacy@flip-vs-cursor-varying-size:
> - shard-tglu: [PASS][4] -> [FAIL][5]
> [4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_19025/shard-tglu-4/igt@kms_cursor_legacy@flip-vs-cursor-varying-size.html
> [5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_172543v1/shard-tglu-6/igt@kms_cursor_legacy@flip-vs-cursor-varying-size.html
>
> * igt@kms_flip@dpms-vs-vblank-race@d-hdmi-a1:
> - shard-tglu: [PASS][6] -> [ABORT][7]
> [6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_19025/shard-tglu-5/igt@kms_flip@dpms-vs-vblank-race@d-hdmi-a1.html
> [7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_172543v1/shard-tglu-7/igt@kms_flip@dpms-vs-vblank-race@d-hdmi-a1.html
>
> * igt@kms_flip@single-buffer-flip-vs-dpms-off-vs-modeset-interruptible:
> - shard-tglu: NOTRUN -> [ABORT][8] +1 other test abort
> [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_172543v1/shard-tglu-8/igt@kms_flip@single-buffer-flip-vs-dpms-off-vs-modeset-interruptible.html
>
> * igt@perf_pmu@semaphore-busy@vcs0:
> - shard-rkl: NOTRUN -> [FAIL][9] +1 other test fail
> [9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_172543v1/shard-rkl-2/igt@perf_pmu@semaphore-busy@vcs0.html
Above failures unrelated to changes. Those platforms don't use MTL or DG2 firmware.
>
> * igt@perf_pmu@semaphore-wait-idle@bcs0:
> - shard-dg2: [PASS][10] -> [FAIL][11] +2 other tests fail
> [10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_19025/shard-dg2-7/igt@perf_pmu@semaphore-wait-idle@bcs0.html
> [11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_172543v1/shard-dg2-6/igt@perf_pmu@semaphore-wait-idle@bcs0.html
Failure related to existing issue, not introduced by this patch.
>
>
> #### Warnings ####
>
> * igt@kms_ccs@missing-ccs-buffer-y-tiled-gen12-mc-ccs:
> - shard-rkl: [SKIP][12] ([i915#14098] / [i915#6095]) -> [ABORT][13]
> [12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_19025/shard-rkl-4/igt@kms_ccs@missing-ccs-buffer-y-tiled-gen12-mc-ccs.html
> [13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_172543v1/shard-rkl-5/igt@kms_ccs@missing-ccs-buffer-y-tiled-gen12-mc-ccs.html
Failures unrelated to changes.
prev parent reply other threads:[~2026-08-26 20:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 19:37 [PATCH] drm/i915/guc: Test GuC v70.74.0 for MTL, DG2 Julia Filipchuk
2026-08-20 19:48 ` sashiko-bot
2026-08-20 21:18 ` ✓ i915.CI.BAT: success for " Patchwork
2026-08-21 2:34 ` ✗ i915.CI.Full: failure " Patchwork
2026-08-26 20:09 ` Julia Filipchuk [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=eeb32ece-43bf-4883-b19a-6d09c6a9ca4f@intel.com \
--to=julia.filipchuk@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