From: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
To: <intel-gfx@lists.freedesktop.org>
Subject: Re: ✗ Fi.CI.BAT: failure for Fix some races/bugs in GuC engine busyness
Date: Tue, 19 Nov 2024 10:46:23 -0800 [thread overview]
Message-ID: <Zzzc/7/FKb/r0I79@orsosgc001> (raw)
In-Reply-To: <173197578749.107654.17859540795040720891@b555e5b46a47>
On Tue, Nov 19, 2024 at 12:23:07AM +0000, Patchwork wrote:
> Patch Details
>
>Series: Fix some races/bugs in GuC engine busyness
>URL: [1]https://patchwork.freedesktop.org/series/141522/
>State: failure
>Details: [2]https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_141522v1/index.html
>
> CI Bug Log - changes from CI_DRM_15717 -> Patchwork_141522v1
>
>Summary
>
> FAILURE
>
> Serious unknown changes coming with Patchwork_141522v1 absolutely need to
> be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_141522v1, 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.
>
> External URL:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_141522v1/index.html
>
>Participating hosts (46 -> 45)
>
> Missing (1): fi-snb-2520m
>
>Possible new issues
>
> Here are the unknown changes that may have been introduced in
> Patchwork_141522v1:
>
> IGT changes
>
> Possible regressions
>
> * igt@i915_pm_rpm@module-reload:
>
> * bat-dg2-11: [3]PASS -> [4]FAIL
> * bat-adls-6: [5]PASS -> [6]FAIL
>
> * igt@i915_selftest@live:
>
> * bat-adlm-1: [7]PASS -> [8]INCOMPLETE
>
> * igt@i915_selftest@live@workarounds:
>
> * bat-mtlp-6: [9]PASS -> [10]ABORT
>
> * igt@kms_pipe_crc_basic@compare-crc-sanitycheck-xr24@pipe-b-dp-2:
>
> * fi-cfl-8109u: [11]PASS -> [12]DMESG-WARN +2 other tests
> dmesg-warn
These are unrelated to fixes in this series and passing locally with the
patches. Queueing a rerun.
Umesh
>
>Known issues
>
next prev parent reply other threads:[~2024-11-19 18:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 23:22 [PATCH 0/3] Fix some races/bugs in GuC engine busyness Umesh Nerlige Ramappa
2024-11-18 23:22 ` [PATCH 1/3] i915/guc: Reset engine utilization buffer before registration Umesh Nerlige Ramappa
2024-11-22 0:29 ` John Harrison
2024-11-18 23:22 ` [PATCH 2/3] i915/guc: Ensure busyness counter increases monotonically Umesh Nerlige Ramappa
2024-11-22 0:31 ` John Harrison
2024-11-22 0:34 ` John Harrison
2024-11-25 20:10 ` Umesh Nerlige Ramappa
2024-11-18 23:22 ` [PATCH 3/3] i915/guc: Accumulate active runtime on gt reset Umesh Nerlige Ramappa
2024-11-22 0:37 ` John Harrison
2024-11-25 20:12 ` Umesh Nerlige Ramappa
2024-11-19 0:04 ` ✗ Fi.CI.SPARSE: warning for Fix some races/bugs in GuC engine busyness Patchwork
2024-11-19 0:23 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-11-19 18:46 ` Umesh Nerlige Ramappa [this message]
2024-11-19 20:04 ` ✗ Fi.CI.SPARSE: warning for Fix some races/bugs in GuC engine busyness (rev2) Patchwork
2024-11-19 20:18 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-11-21 8:38 ` ✗ Fi.CI.SPARSE: warning for Fix some races/bugs in GuC engine busyness (rev3) Patchwork
2024-11-24 9:47 ` ✗ i915.CI.Full: failure " Patchwork
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=Zzzc/7/FKb/r0I79@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