From: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
To: <intel-gfx@lists.freedesktop.org>
Subject: Re: ✗ i915.CI.Full: failure for Fix some races/bugs in GuC engine busyness (rev4)
Date: Thu, 12 Dec 2024 22:28:20 -0800 [thread overview]
Message-ID: <Z1vUBNgnQdQRt/KX@orsosgc001> (raw)
In-Reply-To: <173273976976.3856982.8115235710865638329@b555e5b46a47>
On Wed, Nov 27, 2024 at 08:36:09PM +0000, Patchwork wrote:
> Patch Details
>
>Series: Fix some races/bugs in GuC engine busyness (rev4)
>URL: [1]https://patchwork.freedesktop.org/series/141522/
>State: failure
>Details: [2]https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_141522v4/index.html
>
> CI Bug Log - changes from CI_DRM_15754_full -> Patchwork_141522v4_full
>
>Summary
>
> FAILURE
>
> Serious unknown changes coming with Patchwork_141522v4_full absolutely
> need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_141522v4_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 (12 -> 12)
>
> No changes in participating hosts
>
>Possible new issues
>
> Here are the unknown changes that may have been introduced in
> Patchwork_141522v4_full:
>
> IGT changes
>
> Possible regressions
>
> * igt@gem_eio@in-flight-suspend:
>
> * shard-glk: NOTRUN -> [3]INCOMPLETE
>
> * igt@gem_tiled_swapping@non-threaded:
>
> * shard-glk: NOTRUN -> [4]FAIL
>
> * igt@kms_plane@pixel-format-source-clamping:
>
> * shard-tglu: [5]PASS -> [6]ABORT
>
> * igt@kms_plane@pixel-format-source-clamping@pipe-a-plane-3:
>
> * shard-dg2: [7]PASS -> [8]WARN
above are unrelated.
>
> * igt@perf_pmu@busy-accuracy-50:
>
> * shard-dg1: [9]PASS -> [10]FAIL +3 other tests fail
>
> * igt@perf_pmu@most-busy-idle-check-all@vcs0:
>
> * shard-mtlp: [11]PASS -> [12]FAIL +3 other tests fail
Tried a couple 100 runs of these tests, but did not hit the issue on
MTL. They do not seem related to the changes in this series.
>
> * igt@sysfs_heartbeat_interval@nopreempt:
>
> * shard-mtlp: [13]PASS -> [14]ABORT +1 other test abort
>
> Warnings
>
> * igt@kms_prime@d3hot:
>
> * shard-tglu: [15]SKIP ([16]i915#6524) -> [17]ABORT
unrelated to this series
Thanks,
Umesh
>
>Known issues
next prev parent reply other threads:[~2024-12-13 6:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 17:40 [PATCH 0/3] Fix some races/bugs in GuC engine busyness Umesh Nerlige Ramappa
2024-11-27 17:40 ` [PATCH 1/3] i915/guc: Reset engine utilization buffer before registration Umesh Nerlige Ramappa
2024-11-27 17:40 ` [PATCH 2/3] i915/guc: Ensure busyness counter increases motonically Umesh Nerlige Ramappa
2024-11-27 17:40 ` [PATCH 3/3] i915/guc: Accumulate active runtime on gt reset Umesh Nerlige Ramappa
2024-12-05 22:11 ` John Harrison
2024-11-27 18:42 ` ✗ Fi.CI.SPARSE: warning for Fix some races/bugs in GuC engine busyness (rev4) Patchwork
2024-11-27 18:57 ` ✓ i915.CI.BAT: success " Patchwork
2024-11-27 20:36 ` ✗ i915.CI.Full: failure " Patchwork
2024-12-13 6:28 ` Umesh Nerlige Ramappa [this message]
2024-12-14 0:16 ` [PATCH 0/3] Fix some races/bugs in GuC engine busyness Umesh Nerlige Ramappa
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=Z1vUBNgnQdQRt/KX@orsosgc001 \
--to=umesh.nerlige.ramappa@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