From: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
To: <intel-xe@lists.freedesktop.org>
Subject: Re: ✗ Xe.CI.Full: failure for drm/xe/oa: Ensure that polled read returns latest data
Date: Thu, 20 Feb 2025 17:38:06 -0800 [thread overview]
Message-ID: <Z7fY/pB8zqf4choa@orsosgc001> (raw)
In-Reply-To: <173934530071.1215186.173789869590573127@b555e5b46a47>
On Wed, Feb 12, 2025 at 07:28:20AM +0000, Patchwork wrote:
> Patch Details
>
> Series: drm/xe/oa: Ensure that polled read returns latest data
> URL: [1]https://patchwork.freedesktop.org/series/144684/
> State: failure
> Details: [2]https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-144684v1/index.html
>
>CI Bug Log - changes from xe-2642-76120b67a3d5e7a38cbc92fc39846297130fc6d0_full
> -> xe-pw-144684v1_full
>
>Summary
>
> FAILURE
>
> Serious unknown changes coming with xe-pw-144684v1_full absolutely need to
> be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in xe-pw-144684v1_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-144684v1_full:
>
> IGT changes
>
> Possible regressions
>
> * igt@kms_flip@plain-flip-ts-check-interruptible@a-hdmi-a2:
>
> * shard-dg2-set2: NOTRUN -> [3]FAIL
>
> * igt@kms_rmfb@rmfb-ioctl:
>
> * shard-adlp: [4]PASS -> [5]DMESG-WARN +3 other tests dmesg-warn
The failures are unrelated since the patch touches only the OA path.
Umesh
>
>Known issues
>
prev parent reply other threads:[~2025-02-21 1:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 1:02 [PATCH] drm/xe/oa: Ensure that polled read returns latest data Umesh Nerlige Ramappa
2025-02-12 1:08 ` ✓ CI.Patch_applied: success for " Patchwork
2025-02-12 1:08 ` ✓ CI.checkpatch: " Patchwork
2025-02-12 1:09 ` ✓ CI.KUnit: " Patchwork
2025-02-12 1:38 ` ✓ CI.Build: " Patchwork
2025-02-12 1:41 ` ✓ CI.Hooks: " Patchwork
2025-02-12 1:42 ` ✓ CI.checksparse: " Patchwork
2025-02-12 2:13 ` ✓ Xe.CI.BAT: " Patchwork
2025-02-12 2:27 ` [PATCH] " Dixit, Ashutosh
2025-02-12 16:20 ` Umesh Nerlige Ramappa
2025-02-12 7:28 ` ✗ Xe.CI.Full: failure for " Patchwork
2025-02-21 1:38 ` Umesh Nerlige Ramappa [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=Z7fY/pB8zqf4choa@orsosgc001 \
--to=umesh.nerlige.ramappa@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