Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Aradhya Bhatia <aradhya.bhatia@intel.com>
To: intel-xe@lists.freedesktop.org,
	Tejas Upadhyay <tejas.upadhyay@intel.com>,
	Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>,
	Ayaz A Siddiqui <ayaz.siddiqui@intel.com>
Subject: Re: ✗ Xe.CI.Full: failure for drm/xe/migrate: Switch from drm to dev managed actions
Date: Thu, 27 Mar 2025 17:04:12 +0530	[thread overview]
Message-ID: <9e25e0e7-7c35-41d8-baad-cb9110d38608@intel.com> (raw)
In-Reply-To: <174307418548.10488.18028096142076320099@e6b6f09ec485>

Hi,

On 27-03-2025 16:46, Patchwork wrote:
> == Series Details ==
> 
> Series: drm/xe/migrate: Switch from drm to dev managed actions
> URL   : https://patchwork.freedesktop.org/series/146811/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from xe-2854-14c330bc015ded4a1f1dd1f5aeb8617077aaa7e8_FULL -> xe-pw-146811v1_FULL
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with xe-pw-146811v1_FULL absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in xe-pw-146811v1_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-146811v1_FULL:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####
> 
>   * igt@kms_ccs@random-ccs-data-4-tiled-dg2-rc-ccs-cc@pipe-d-dp-4:
>     - shard-dg2-set2:     NOTRUN -> [INCOMPLETE][1]
>    [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-146811v1/shard-dg2-435/igt@kms_ccs@random-ccs-data-4-tiled-dg2-rc-ccs-cc@pipe-d-dp-4.html
> 
>   * igt@kms_plane_multiple@2x-tiling-none:
>     - shard-lnl:          NOTRUN -> [SKIP][2] +5 other tests skip
>    [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-146811v1/shard-lnl-6/igt@kms_plane_multiple@2x-tiling-none.html
> 
>   * igt@kms_plane_multiple@2x-tiling-yf:
>     - shard-adlp:         NOTRUN -> [SKIP][3] +4 other tests skip
>    [3]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-146811v1/shard-adlp-8/igt@kms_plane_multiple@2x-tiling-yf.html
>     - shard-bmg:          NOTRUN -> [SKIP][4] +2 other tests skip
>    [4]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-146811v1/shard-bmg-6/igt@kms_plane_multiple@2x-tiling-yf.html
> 
>   * igt@xe_fault_injection@oa-add-config-fail-xe_oa_alloc_regs (NEW):
>     - shard-dg2-set2:     NOTRUN -> [FAIL][5]
>    [5]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-146811v1/shard-dg2-436/igt@xe_fault_injection@oa-add-config-fail-xe_oa_alloc_regs.html
>     - shard-lnl:          NOTRUN -> [FAIL][6]
>    [6]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-146811v1/shard-lnl-5/igt@xe_fault_injection@oa-add-config-fail-xe_oa_alloc_regs.html
>     - shard-adlp:         NOTRUN -> [FAIL][7]
>    [7]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-146811v1/shard-adlp-1/igt@xe_fault_injection@oa-add-config-fail-xe_oa_alloc_regs.html
>     - shard-bmg:          NOTRUN -> [FAIL][8]
>    [8]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-146811v1/shard-bmg-3/igt@xe_fault_injection@oa-add-config-fail-xe_oa_alloc_regs.html
> 
>   
> #### Warnings ####
> 
>   * igt@kms_ccs@random-ccs-data-4-tiled-dg2-rc-ccs-cc:
>     - shard-dg2-set2:     [INCOMPLETE][9] ([Intel XE#2705]) -> [INCOMPLETE][10]
>    [9]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2854-14c330bc015ded4a1f1dd1f5aeb8617077aaa7e8/shard-dg2-433/igt@kms_ccs@random-ccs-data-4-tiled-dg2-rc-ccs-cc.html
>    [10]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-146811v1/shard-dg2-435/igt@kms_ccs@random-ccs-data-4-tiled-dg2-rc-ccs-cc.html
> 
>   

These possible regressions do not seem related to my patch.

Please go ahead with the merge. Thanks!

--
Regards
Aradhya


[snip]




      reply	other threads:[~2025-03-27 11:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-26 15:19 [RESEND PATCH v2] drm/xe/migrate: Switch from drm to dev managed actions Aradhya Bhatia
2025-03-26 16:11 ` ✓ CI.Patch_applied: success for " Patchwork
2025-03-26 16:11 ` ✓ CI.checkpatch: " Patchwork
2025-03-26 16:12 ` ✓ CI.KUnit: " Patchwork
2025-03-26 16:29 ` ✓ CI.Build: " Patchwork
2025-03-26 16:31 ` ✓ CI.Hooks: " Patchwork
2025-03-26 16:33 ` ✓ CI.checksparse: " Patchwork
2025-03-26 16:53 ` ✓ Xe.CI.BAT: " Patchwork
2025-03-27  5:52 ` ✗ Xe.CI.Full: failure " Patchwork
2025-03-27  8:47 ` Patchwork
2025-03-27 11:16 ` Patchwork
2025-03-27 11:34   ` Aradhya Bhatia [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=9e25e0e7-7c35-41d8-baad-cb9110d38608@intel.com \
    --to=aradhya.bhatia@intel.com \
    --cc=ayaz.siddiqui@intel.com \
    --cc=himal.prasad.ghimiray@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=tejas.upadhyay@intel.com \
    /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