Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 (rev4)
Date: Mon, 24 Feb 2025 12:47:22 -0800	[thread overview]
Message-ID: <Z7za2kXHi4rd2CNF@orsosgc001> (raw)
In-Reply-To: <174022676882.744357.2803819277386187999@b555e5b46a47>

On Sat, Feb 22, 2025 at 12:19:28PM +0000, Patchwork wrote:
>   Patch Details
>
> Series:  drm/xe/oa: Allow oa_exponent value of 0 (rev4)
> URL:     [1]https://patchwork.freedesktop.org/series/144685/
> State:   failure
> Details: [2]https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-144685v4/index.html
>
>CI Bug Log - changes from xe-2700-f2a2bd676bde0942c9dfe5c55d54eec298260f88_full
>                             -> xe-pw-144685v4_full
>
>Summary
>
>   FAILURE
>
>   Serious unknown changes coming with xe-pw-144685v4_full absolutely need to
>   be
>   verified manually.
>
>   If you think the reported changes have nothing to do with the changes
>   introduced in xe-pw-144685v4_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-144685v4_full:
>
>  IGT changes
>
>    Possible regressions
>
>     * igt@kms_sequence@queue-idle@pipe-b-dp-4:
>
>          * shard-dg2-set2: [3]PASS -> [4]INCOMPLETE +2 other tests
>            incomplete
>
>     * igt@kms_universal_plane@cursor-fb-leak:
>
>          * shard-adlp: [5]PASS -> [6]DMESG-WARN +3 other tests dmesg-warn
>
>     * igt@xe_spin_batch@spin-timestamp-check@engine-drm_xe_engine_class_video_decode:
>
>          * shard-dg2-set2: [7]PASS -> [8]DMESG-WARN
>
>    Warnings
>
>     * igt@kms_vblank@query-busy:
>
>          * shard-dg2-set2: [9]DMESG-WARN ([10]Intel XE#4330) ->
>            [11]INCOMPLETE

These failures are unrelated to this patch.

Umesh

>
>New tests
...
>
>Known issues
>
...

      reply	other threads:[~2025-02-24 20:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-21 21:33 [PATCH v4] drm/xe/oa: Allow oa_exponent value of 0 Umesh Nerlige Ramappa
2025-02-21 22:23 ` ✓ CI.Patch_applied: success for drm/xe/oa: Allow oa_exponent value of 0 (rev4) Patchwork
2025-02-21 22:23 ` ✓ CI.checkpatch: " Patchwork
2025-02-21 22:24 ` ✓ CI.KUnit: " Patchwork
2025-02-21 22:42 ` ✓ CI.Build: " Patchwork
2025-02-21 22:44 ` ✓ CI.Hooks: " Patchwork
2025-02-21 22:45 ` ✓ CI.checksparse: " Patchwork
2025-02-21 23:12 ` ✓ Xe.CI.BAT: " Patchwork
2025-02-22 12:19 ` ✗ Xe.CI.Full: failure " Patchwork
2025-02-24 20:47   ` 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=Z7za2kXHi4rd2CNF@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