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/xe2hpg: Add Wa_16025250150 (rev2)
Date: Fri, 28 Mar 2025 12:06:12 +0530 [thread overview]
Message-ID: <363df5cc-0be6-44d4-b515-6070ad35d5cd@intel.com> (raw)
In-Reply-To: <174311817504.13007.12492813581667605313@e6b6f09ec485>
Hi,
On 28-03-2025 04:59, Patchwork wrote:
> == Series Details ==
>
> Series: drm/xe/xe2hpg: Add Wa_16025250150 (rev2)
> URL : https://patchwork.freedesktop.org/series/146709/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from xe-2859-1e750490a76bbb8bcb8ea8d5fba2a68bf0845def_FULL -> xe-pw-146709v2_FULL
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with xe-pw-146709v2_FULL absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in xe-pw-146709v2_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-146709v2_FULL:
>
> ### IGT changes ###
>
> #### Possible regressions ####
>
> * igt@kms_flip_scaled_crc@flip-64bpp-linear-to-16bpp-linear-upscaling:
> - shard-lnl: [PASS][1] -> ([PASS][2], [INCOMPLETE][3]) +1 other test ( 1 incomplete, 1 pass )
> [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2859-1e750490a76bbb8bcb8ea8d5fba2a68bf0845def/shard-lnl-2/igt@kms_flip_scaled_crc@flip-64bpp-linear-to-16bpp-linear-upscaling.html
> [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-146709v2/shard-lnl-4/igt@kms_flip_scaled_crc@flip-64bpp-linear-to-16bpp-linear-upscaling.html
> [3]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-146709v2/shard-lnl-1/igt@kms_flip_scaled_crc@flip-64bpp-linear-to-16bpp-linear-upscaling.html
>
> * igt@kms_plane_multiple@2x-tiling-yf:
> - shard-lnl: NOTRUN -> [SKIP][4]
> [4]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-146709v2/shard-lnl-8/igt@kms_plane_multiple@2x-tiling-yf.html
>
> * igt@kms_vblank@query-busy-hang:
> - shard-dg2-set2: [PASS][5] -> ([INCOMPLETE][6], [PASS][7]) +2 other tests ( 1 incomplete, 1 pass )
> [5]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2859-1e750490a76bbb8bcb8ea8d5fba2a68bf0845def/shard-dg2-464/igt@kms_vblank@query-busy-hang.html
> [6]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-146709v2/shard-dg2-432/igt@kms_vblank@query-busy-hang.html
> [7]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-146709v2/shard-dg2-463/igt@kms_vblank@query-busy-hang.html
>
> * igt@kms_vblank@query-busy-hang@pipe-d-dp-2:
> - shard-dg2-set2: NOTRUN -> [INCOMPLETE][8]
> [8]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-146709v2/shard-dg2-432/igt@kms_vblank@query-busy-hang@pipe-d-dp-2.html
>
> * igt@xe_exec_sip_eudebug@wait-writesip-nodebug@drm_xe_engine_class_compute0:
> - shard-lnl: [PASS][9] -> [INCOMPLETE][10] +1 other test incomplete
> [9]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2859-1e750490a76bbb8bcb8ea8d5fba2a68bf0845def/shard-lnl-4/igt@xe_exec_sip_eudebug@wait-writesip-nodebug@drm_xe_engine_class_compute0.html
> [10]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-146709v2/shard-lnl-7/igt@xe_exec_sip_eudebug@wait-writesip-nodebug@drm_xe_engine_class_compute0.html
>
> * igt@xe_fault_injection@exec-queue-create-fail-xe_hw_engine_group_add_exec_queue:
> - shard-bmg: [PASS][11] -> ([PASS][12], [ABORT][13])
> [11]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2859-1e750490a76bbb8bcb8ea8d5fba2a68bf0845def/shard-bmg-4/igt@xe_fault_injection@exec-queue-create-fail-xe_hw_engine_group_add_exec_queue.html
> [12]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-146709v2/shard-bmg-3/igt@xe_fault_injection@exec-queue-create-fail-xe_hw_engine_group_add_exec_queue.html
> [13]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-146709v2/shard-bmg-4/igt@xe_fault_injection@exec-queue-create-fail-xe_hw_engine_group_add_exec_queue.html
> - shard-dg2-set2: [PASS][14] -> ([ABORT][15], [PASS][16])
> [14]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2859-1e750490a76bbb8bcb8ea8d5fba2a68bf0845def/shard-dg2-435/igt@xe_fault_injection@exec-queue-create-fail-xe_hw_engine_group_add_exec_queue.html
> [15]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-146709v2/shard-dg2-435/igt@xe_fault_injection@exec-queue-create-fail-xe_hw_engine_group_add_exec_queue.html
> [16]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-146709v2/shard-dg2-436/igt@xe_fault_injection@exec-queue-create-fail-xe_hw_engine_group_add_exec_queue.html
>
These possible regressions do not seem to be related to my patch.
--
Regards
Aradhya
prev parent reply other threads:[~2025-03-28 6:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 13:44 [PATCH v2] drm/xe/xe2hpg: Add Wa_16025250150 Aradhya Bhatia
2025-03-25 14:17 ` ✓ CI.Patch_applied: success for drm/xe/xe2hpg: Add Wa_16025250150 (rev2) Patchwork
2025-03-25 14:17 ` ✓ CI.checkpatch: " Patchwork
2025-03-25 14:19 ` ✓ CI.KUnit: " Patchwork
2025-03-25 14:35 ` ✓ CI.Build: " Patchwork
2025-03-25 14:37 ` ✓ CI.Hooks: " Patchwork
2025-03-25 14:39 ` ✓ CI.checksparse: " Patchwork
2025-03-25 20:28 ` ✗ Xe.CI.Full: failure " Patchwork
2025-03-27 14:36 ` ✓ CI.Patch_applied: success " Patchwork
2025-03-27 14:36 ` ✓ CI.checkpatch: " Patchwork
2025-03-27 14:37 ` ✓ CI.KUnit: " Patchwork
2025-03-27 14:54 ` ✓ CI.Build: " Patchwork
2025-03-27 14:56 ` ✓ CI.Hooks: " Patchwork
2025-03-27 14:57 ` ✓ CI.checksparse: " Patchwork
2025-03-27 15:18 ` ✗ Xe.CI.BAT: failure " Patchwork
2025-04-03 4:52 ` Aradhya Bhatia
2025-03-27 23:29 ` ✗ Xe.CI.Full: " Patchwork
2025-03-28 6:36 ` 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=363df5cc-0be6-44d4-b515-6070ad35d5cd@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