From: Jani Nikula <jani.nikula@intel.com>
To: ville.syrjala@linux.intel.com
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ i915.CI.Full: failure for drm/i915/display: stop using the configurable fence timeout, cleanups
Date: Tue, 15 Sep 2026 12:00:15 +0300 [thread overview]
Message-ID: <d520355171afa55a704332c3439b398d1ea8c998@intel.com> (raw)
In-Reply-To: <178915420733.152712.10400122725172881029@61270ab9df2a>
On Fri, 11 Sep 2026, Patchwork <patchwork@emeril.freedesktop.org> wrote:
> Possible new issues
> -------------------
>
> Here are the unknown changes that may have been introduced in Patchwork_173812v1_full:
>
> ### IGT changes ###
>
> #### Possible regressions ####
>
> * igt@gem_ctx_persistence@engines-mixed-process@vcs1:
> - shard-mtlp: [PASS][1] -> [ABORT][2] +1 other test abort
> [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_19124/shard-mtlp-4/igt@gem_ctx_persistence@engines-mixed-process@vcs1.html
> [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_173812v1/shard-mtlp-3/igt@gem_ctx_persistence@engines-mixed-process@vcs1.html
>
> * igt@gem_ctx_persistence@engines-mixed-process@vecs0:
> - shard-mtlp: [PASS][3] -> [DMESG-WARN][4]
> [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_19124/shard-mtlp-4/igt@gem_ctx_persistence@engines-mixed-process@vecs0.html
> [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_173812v1/shard-mtlp-3/igt@gem_ctx_persistence@engines-mixed-process@vecs0.html
>
> * igt@perf_pmu@rc6@runtime-pm-long-gt1:
> - shard-mtlp: [PASS][5] -> [FAIL][6] +5 other tests fail
> [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_19124/shard-mtlp-2/igt@perf_pmu@rc6@runtime-pm-long-gt1.html
> [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_173812v1/shard-mtlp-7/igt@perf_pmu@rc6@runtime-pm-long-gt1.html
These look worrying, but I'm not sure how the patches at hand could
cause them on MTL.
Ville, ack on merging the series?
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2026-09-15 9:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 19:42 [PATCH 0/4] drm/i915/display: stop using the configurable fence timeout, cleanups Jani Nikula
2026-09-10 19:42 ` [PATCH 1/4] drm/i915/display: stop using the configurable fence timeout Jani Nikula
2026-09-10 19:42 ` [PATCH 2/4] drm/i915/display: use struct intel_atomic_state *state variable naming Jani Nikula
2026-09-15 6:00 ` Kandpal, Suraj
2026-09-10 19:42 ` [PATCH 3/4] drm/i915/display: reduce indent in intel_atomic_commit_fence_wait() Jani Nikula
2026-09-15 6:01 ` Kandpal, Suraj
2026-09-10 19:42 ` [PATCH 4/4] drm/i915/display: debug log about fence wait errors Jani Nikula
2026-09-15 6:02 ` Kandpal, Suraj
2026-09-10 23:37 ` ✓ i915.CI.BAT: success for drm/i915/display: stop using the configurable fence timeout, cleanups Patchwork
2026-09-11 19:16 ` ✗ i915.CI.Full: failure " Patchwork
2026-09-15 9:00 ` Jani Nikula [this message]
2026-09-17 12:46 ` [PATCH 0/4] " Jani Nikula
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=d520355171afa55a704332c3439b398d1ea8c998@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@linux.intel.com \
/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