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: Allow oa_exponent value of 0 (rev2)
Date: Fri, 21 Feb 2025 12:38:40 -0800 [thread overview]
Message-ID: <Z7jkUMbQNjfzATQt@orsosgc001> (raw)
In-Reply-To: <173941596458.1508100.5238417724237785982@b555e5b46a47>
On Thu, Feb 13, 2025 at 03:06:04AM +0000, Patchwork wrote:
> Patch Details
>
> Series: drm/xe/oa: Allow oa_exponent value of 0 (rev2)
> URL: [1]https://patchwork.freedesktop.org/series/144685/
> State: failure
> Details: [2]https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-144685v2/index.html
>
>CI Bug Log - changes from xe-2649-cbd90e3e74e3102b4a3eeca23e0136382e8a478f_full
> -> xe-pw-144685v2_full
>
>Summary
>
> FAILURE
>
> Serious unknown changes coming with xe-pw-144685v2_full absolutely need to
> be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in xe-pw-144685v2_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-144685v2_full:
>
> IGT changes
>
> Possible regressions
>
> * igt@kms_ccs@crc-primary-suspend-4-tiled-bmg-ccs:
>
> * shard-bmg: [3]PASS -> [4]DMESG-WARN
>
> * igt@kms_cursor_legacy@cursor-vs-flip-atomic-transitions-varying-size:
>
> * shard-adlp: [5]PASS -> [6]DMESG-WARN
>
> * igt@xe_oa@mi-rpc:
>
> * shard-lnl: [7]PASS -> [8]FAIL +2 other tests fail
> * shard-bmg: [9]PASS -> [10]FAIL
This is a bug from this patch. Will post a fix
Umesh
>
> * igt@xe_oa@non-sampling-read-error:
>
> * shard-bmg: NOTRUN -> [11]FAIL +1 other test fail
>
> * igt@xe_pm@s2idle-vm-bind-prefetch:
>
> * shard-dg2-set2: [12]PASS -> [13]ABORT
>
>New tests
prev parent reply other threads:[~2025-02-21 20:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 16:26 [PATCH v2] drm/xe/oa: Allow oa_exponent value of 0 Umesh Nerlige Ramappa
2025-02-12 17:17 ` Dixit, Ashutosh
2025-02-12 17:44 ` Dixit, Ashutosh
2025-02-12 18:53 ` ✓ CI.Patch_applied: success for drm/xe/oa: Allow oa_exponent value of 0 (rev2) Patchwork
2025-02-12 18:53 ` ✓ CI.checkpatch: " Patchwork
2025-02-12 18:54 ` ✓ CI.KUnit: " Patchwork
2025-02-12 19:11 ` ✓ CI.Build: " Patchwork
2025-02-12 19:13 ` ✓ CI.Hooks: " Patchwork
2025-02-12 19:15 ` ✓ CI.checksparse: " Patchwork
2025-02-12 19:35 ` ✓ Xe.CI.BAT: " Patchwork
2025-02-13 3:06 ` ✗ Xe.CI.Full: failure " Patchwork
2025-02-21 20: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=Z7jkUMbQNjfzATQt@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