Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
To: <igt-dev@lists.freedesktop.org>
Subject: Re: ✗ i915.CI.Full: failure for tests/intel/xe_oa: Print oa_status value in the helper
Date: Thu, 27 Mar 2025 11:48:26 -0700	[thread overview]
Message-ID: <Z+Wdeksxw2RjF6bF@soc-5CG1426VCC.clients.intel.com> (raw)
In-Reply-To: <174303689612.9111.5084313516886304936@e6b6f09ec485>

On Thu, Mar 27, 2025 at 12:54:56AM +0000, Patchwork wrote:
>   Patch Details
>
>   Series:  tests/intel/xe_oa: Print oa_status value in the helper          
>   URL:     https://patchwork.freedesktop.org/series/146829/                
>   State:   failure                                                         
>   Details: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12847/index.html 
>
>          CI Bug Log - changes from IGT_8288_full -> IGTPW_12847_full
>
>Summary
>
>   FAILURE
>
>   Serious unknown changes coming with IGTPW_12847_full absolutely need to be
>   verified manually.
>
>   If you think the reported changes have nothing to do with the changes
>   introduced in IGTPW_12847_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.
>
>   External URL:
>   https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_12847/index.html
>
>Participating hosts (10 -> 10)
>
>   No changes in participating hosts
>
>Possible new issues
>
>   Here are the unknown changes that may have been introduced in
>   IGTPW_12847_full:
>
>  IGT changes
>
>    Possible regressions
>
>     * igt@gem_workarounds@suspend-resume-fd:
>
>          * shard-glk: NOTRUN -> INCOMPLETE
>     * igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size:
>
>          * shard-rkl: NOTRUN -> FAIL
>     * igt@kms_flip@flip-vs-suspend@a-hdmi-a2:
>
>          * shard-rkl: NOTRUN -> INCOMPLETE
>     * igt@kms_plane@plane-panning-bottom-right-suspend@pipe-a:
>
>          * shard-rkl: PASS -> INCOMPLETE +1 other test incomplete
>     * igt@kms_plane_multiple@2x-tiling-4:
>
>          * shard-dg2: NOTRUN -> SKIP +1 other test skip
>     * igt@kms_plane_multiple@2x-tiling-x:
>
>          * shard-dg2-9: NOTRUN -> SKIP
>          * shard-tglu-1: NOTRUN -> SKIP
>     * igt@kms_plane_multiple@2x-tiling-y:
>
>          * shard-rkl: NOTRUN -> SKIP +2 other tests skip
>     * igt@kms_plane_multiple@2x-tiling-yf:
>
>          * shard-tglu: NOTRUN -> SKIP

Unrelated since the patch here only modifies xe_oa test.

Umesh
>
>New tests
>

  reply	other threads:[~2025-03-27 18:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-26 22:17 [PATCH i-g-t] tests/intel/xe_oa: Print oa_status value in the helper Umesh Nerlige Ramappa
2025-03-26 22:24 ` Dixit, Ashutosh
2025-03-26 22:28   ` Umesh Nerlige Ramappa
2025-03-26 22:56 ` ✓ Xe.CI.BAT: success for " Patchwork
2025-03-26 23:14 ` ✓ i915.CI.BAT: " Patchwork
2025-03-27  0:54 ` ✗ i915.CI.Full: failure " Patchwork
2025-03-27 18:48   ` Umesh Nerlige Ramappa [this message]
2025-03-27 13:04 ` ✗ Xe.CI.Full: " Patchwork
2025-03-28 11:42 ` Patchwork
2025-04-06 16:17 ` 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=Z+Wdeksxw2RjF6bF@soc-5CG1426VCC.clients.intel.com \
    --to=umesh.nerlige.ramappa@intel.com \
    --cc=igt-dev@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