From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: <intel-xe@lists.freedesktop.org>
Subject: Re: ✗ CI.FULL: failure for drm/xe/oa: Fix "Missing outer runtime PM protection" warning
Date: Tue, 12 Nov 2024 12:34:08 -0800 [thread overview]
Message-ID: <85frnwxkcf.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <173121283512.1946529.16242559266326275382@2413ebb6fbb6>
On Sat, 09 Nov 2024 20:27:15 -0800, Patchwork wrote:
>
> Series: drm/xe/oa: Fix "Missing outer runtime PM protection" warning
> URL: https://patchwork.freedesktop.org/series/141123/
> State: failure
> Details: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-141123v1/index.html
>
> CI Bug Log - changes from xe-2194-00976833a8b163cfcad247ba2d22ea4819fd749c_full -> xe-pw-141123v1_full
>
> Summary
>
> FAILURE
>
> Serious unknown changes coming with xe-pw-141123v1_full absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in xe-pw-141123v1_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 (4 -> 4)
>
> No changes in participating hosts
>
> Possible new issues
>
> Here are the unknown changes that may have been introduced in xe-pw-141123v1_full:
>
> IGT changes
>
> Possible regressions
>
> * igt@kms_content_protection@atomic@pipe-a-dp-5:
>
> * shard-dg2-set2: NOTRUN -> FAIL +2 other tests fail
>
> * igt@kms_plane@pixel-format-source-clamping@pipe-b-plane-3:
>
> * shard-bmg: NOTRUN -> INCOMPLETE
>
> * igt@kms_rotation_crc@sprite-rotation-90:
>
> * shard-bmg: NOTRUN -> SKIP
>
> Warnings
>
> * igt@kms_rotation_crc@bad-pixel-format:
>
> * shard-dg2-set2: SKIP (Intel XE#2423 / i915#2575) -> SKIP
Unrelated, will wait a bit and then merge the patch.
prev parent reply other threads:[~2024-11-12 20:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-09 3:20 [PATCH] drm/xe/oa: Fix "Missing outer runtime PM protection" warning Ashutosh Dixit
2024-11-09 3:25 ` ✓ CI.Patch_applied: success for " Patchwork
2024-11-09 3:25 ` ✓ CI.checkpatch: " Patchwork
2024-11-09 3:27 ` ✓ CI.KUnit: " Patchwork
2024-11-09 3:38 ` ✓ CI.Build: " Patchwork
2024-11-09 3:40 ` ✓ CI.Hooks: " Patchwork
2024-11-09 3:42 ` ✓ CI.checksparse: " Patchwork
2024-11-09 4:00 ` ✓ CI.BAT: " Patchwork
2024-11-09 5:09 ` [PATCH] " Matthew Brost
2024-11-10 4:27 ` ✗ CI.FULL: failure for " Patchwork
2024-11-12 20:34 ` Dixit, Ashutosh [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=85frnwxkcf.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=intel-xe@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