From: "Modem, Bhanuprakash" <bhanuprakash.modem@intel.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
<igt-dev@lists.freedesktop.org>,
Andrzej Hajda <andrzej.hajda@intel.com>,
<I915-ci-infra@lists.freedesktop.org>,
Jari Tahvanainen <jari.tahvanainen@intel.com>
Subject: Re: ✗ CI.xeBAT: failure for lib/gpgpu: add shader support (rev7)
Date: Tue, 18 Jun 2024 15:25:30 +0530 [thread overview]
Message-ID: <03c9094e-1fb6-4cba-8da3-2628a967c4b5@intel.com> (raw)
In-Reply-To: <20240614132731.vizhnvphj22kyek5@kamilkon-DESK.igk.intel.com>
On 14-06-2024 06:57 pm, Kamil Konieczny wrote:
> Hi igt-dev,
> On 2024-06-12 at 10:18:52 -0000, Patchwork wrote:
>> == Series Details ==
>>
>> Series: lib/gpgpu: add shader support (rev7)
>> URL : https://patchwork.freedesktop.org/series/133020/
>> State : failure
>>
>> == Summary ==
>>
>> CI Bug Log - changes from XEIGT_7882_BAT -> XEIGTPW_11252_BAT
>> ====================================================
>>
>> Summary
>> -------
>>
>> **FAILURE**
>>
>> Serious unknown changes coming with XEIGTPW_11252_BAT absolutely need to be
>> verified manually.
>>
>> If you think the reported changes have nothing to do with the changes
>> introduced in XEIGTPW_11252_BAT, 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 -> 1)
>> ------------------------------
>>
>> ERROR: It appears as if the changes made in XEIGTPW_11252_BAT prevented too many machines from booting.
>>
>> Additional (1): bat-pvc-2
>> Missing (4): bat-atsm-2 bat-dg2-oem2 bat-lnl-1 bat-adlp-7
>
> This is unlikly.
>
>>
>> Known issues
>> ------------
>>
>> Here are the changes found in XEIGTPW_11252_BAT that come from known issues:
>>
>> ### IGT changes ###
>>
>> #### Issues hit ####
>>
>> * igt@kms_addfb_basic@addfb25-x-tiled-legacy:
>> - bat-pvc-2: NOTRUN -> [SKIP][1] ([i915#6077]) +30 other tests skip
>> [1]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_11252/bat-pvc-2/igt@kms_addfb_basic@addfb25-x-tiled-legacy.html
>>
>
> imho PVC has no display so all kms tests should be blocklisted
> for this particular GPU. Adding Bhanu and Jari to cc.
I'm not sure we have a platform specific blocklist?
- Bhanu
>
> Regards,
> Kamil
>
>> * igt@kms_cursor_legacy@basic-flip-after-cursor-atomic:
>> - bat-pvc-2: NOTRUN -> [SKIP][2] ([Intel XE#1024] / [Intel XE#782]) +5 other tests skip
>> [2]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_11252/bat-pvc-2/igt@kms_cursor_legacy@basic-flip-after-cursor-atomic.html
>>
>> * igt@kms_dsc@dsc-basic:
>> - bat-pvc-2: NOTRUN -> [SKIP][3] ([Intel XE#1024] / [Intel XE#784])
>> [3]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_11252/bat-pvc-2/igt@kms_dsc@dsc-basic.html
>>
>> * igt@kms_flip@basic-flip-vs-dpms:
>> - bat-pvc-2: NOTRUN -> [SKIP][4] ([Intel XE#1024] / [Intel XE#947]) +3 other tests skip
>> [4]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_11252/bat-pvc-2/igt@kms_flip@basic-flip-vs-dpms.html
>>
>> * igt@kms_force_connector_basic@force-connector-state:
>> - bat-pvc-2: NOTRUN -> [SKIP][5] ([Intel XE#540]) +3 other tests skip
>> [5]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_11252/bat-pvc-2/igt@kms_force_connector_basic@force-connector-state.html
>>
>> * igt@kms_frontbuffer_tracking@basic:
>> - bat-pvc-2: NOTRUN -> [SKIP][6] ([Intel XE#1024] / [Intel XE#783])
>> [6]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_11252/bat-pvc-2/igt@kms_frontbuffer_tracking@basic.html
>>
>> * igt@kms_pipe_crc_basic@nonblocking-crc-frame-sequence:
>> - bat-pvc-2: NOTRUN -> [SKIP][7] ([Intel XE#829]) +6 other tests skip
>> [7]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_11252/bat-pvc-2/igt@kms_pipe_crc_basic@nonblocking-crc-frame-sequence.html
>>
>> * igt@kms_prop_blob@basic:
>> - bat-pvc-2: NOTRUN -> [SKIP][8] ([Intel XE#780])
>> [8]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_11252/bat-pvc-2/igt@kms_prop_blob@basic.html
>>
>> * igt@kms_psr@psr-cursor-plane-move:
>> - bat-pvc-2: NOTRUN -> [SKIP][9] ([Intel XE#1024]) +2 other tests skip
>> [9]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_11252/bat-pvc-2/igt@kms_psr@psr-cursor-plane-move.html
>>
>> * igt@xe_evict@evict-beng-small-external:
>> - bat-pvc-2: NOTRUN -> [FAIL][10] ([Intel XE#1000]) +3 other tests fail
>> [10]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_11252/bat-pvc-2/igt@xe_evict@evict-beng-small-external.html
>>
>> * igt@xe_evict@evict-small-cm:
>> - bat-pvc-2: NOTRUN -> [DMESG-FAIL][11] ([Intel XE#482]) +3 other tests dmesg-fail
>> [11]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_11252/bat-pvc-2/igt@xe_evict@evict-small-cm.html
>>
>> * igt@xe_gt_freq@freq_range_idle:
>> - bat-pvc-2: NOTRUN -> [SKIP][12] ([Intel XE#1021]) +1 other test skip
>> [12]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_11252/bat-pvc-2/igt@xe_gt_freq@freq_range_idle.html
>>
>> * igt@xe_huc_copy@huc_copy:
>> - bat-pvc-2: NOTRUN -> [SKIP][13] ([Intel XE#255])
>> [13]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_11252/bat-pvc-2/igt@xe_huc_copy@huc_copy.html
>>
>> * igt@xe_intel_bb@render:
>> - bat-pvc-2: NOTRUN -> [SKIP][14] ([Intel XE#532])
>> [14]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_11252/bat-pvc-2/igt@xe_intel_bb@render.html
>>
>> * igt@xe_pat@pat-index-xe2:
>> - bat-pvc-2: NOTRUN -> [SKIP][15] ([Intel XE#977]) +1 other test skip
>> [15]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_11252/bat-pvc-2/igt@xe_pat@pat-index-xe2.html
>>
>> * igt@xe_pat@pat-index-xehpc@render:
>> - bat-pvc-2: NOTRUN -> [SKIP][16] ([Intel XE#976])
>> [16]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_11252/bat-pvc-2/igt@xe_pat@pat-index-xehpc@render.html
>>
>> * igt@xe_pat@pat-index-xelpg:
>> - bat-pvc-2: NOTRUN -> [SKIP][17] ([Intel XE#979])
>> [17]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_11252/bat-pvc-2/igt@xe_pat@pat-index-xelpg.html
>>
>> * igt@xe_pm_residency@gt-c6-on-idle:
>> - bat-pvc-2: NOTRUN -> [SKIP][18] ([Intel XE#531])
>> [18]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_11252/bat-pvc-2/igt@xe_pm_residency@gt-c6-on-idle.html
>>
>>
>> [Intel XE#1000]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1000
>> [Intel XE#1021]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1021
>> [Intel XE#1024]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1024
>> [Intel XE#255]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/255
>> [Intel XE#482]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/482
>> [Intel XE#531]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/531
>> [Intel XE#532]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/532
>> [Intel XE#540]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/540
>> [Intel XE#780]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/780
>> [Intel XE#782]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/782
>> [Intel XE#783]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/783
>> [Intel XE#784]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/784
>> [Intel XE#829]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/829
>> [Intel XE#947]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/947
>> [Intel XE#976]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/976
>> [Intel XE#977]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/977
>> [Intel XE#979]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/979
>> [i915#6077]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/6077
>>
>>
>> Build changes
>> -------------
>>
>> * IGT: IGT_7882 -> IGTPW_11252
>> * Linux: xe-1444-950ce28fe0b31a24c5bddcc337aba9554a41cbb3 -> xe-1447-86b413568d7dbde6078f6c40341f5ae1ae63c552
>>
>> IGTPW_11252: 11252
>> IGT_7882: 257418cba11c724111fe0e983649763c407e5bc9 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
>> xe-1444-950ce28fe0b31a24c5bddcc337aba9554a41cbb3: 950ce28fe0b31a24c5bddcc337aba9554a41cbb3
>> xe-1447-86b413568d7dbde6078f6c40341f5ae1ae63c552: 86b413568d7dbde6078f6c40341f5ae1ae63c552
>>
>> == Logs ==
>>
>> For more details see: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_11252/index.html
next prev parent reply other threads:[~2024-06-18 9:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 9:38 [PATCH v7 0/5] lib/gpgpu: add shader support Andrzej Hajda
2024-06-12 9:38 ` [PATCH v7 1/5] lib/gpu_cmds: add Xe_LP version of emit_vfe_state Andrzej Hajda
2024-06-17 10:51 ` Zbigniew Kempczyński
2024-06-12 9:39 ` [PATCH v7 2/5] lib/gpgpu_shader: tooling for preparing and running gpgpu shaders Andrzej Hajda
2024-06-17 11:41 ` Zbigniew Kempczyński
2024-06-12 9:39 ` [PATCH v7 3/5] lib/gpgpu_shader: add inline support for iga64 assembly Andrzej Hajda
2024-06-19 6:40 ` Zbigniew Kempczyński
2024-06-19 9:08 ` Andrzej Hajda
2024-06-12 9:39 ` [PATCH v7 4/5] lib/igt_sysfs: add helpers to access engine sysfs directory Andrzej Hajda
2024-06-12 12:59 ` Kamil Konieczny
2024-06-17 14:04 ` Zbigniew Kempczyński
2024-06-27 7:39 ` Andrzej Hajda
2024-06-12 9:39 ` [PATCH v7 5/5] intel/xe_exec_sip: add shader sanity test Andrzej Hajda
2024-06-12 10:18 ` ✗ CI.xeBAT: failure for lib/gpgpu: add shader support (rev7) Patchwork
2024-06-14 13:27 ` Kamil Konieczny
2024-06-18 9:55 ` Modem, Bhanuprakash [this message]
2024-06-12 10:33 ` ✓ Fi.CI.BAT: success " Patchwork
2024-06-12 11:21 ` ✓ CI.xeFULL: " Patchwork
2024-06-13 8:20 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-06-14 13:22 ` Kamil Konieczny
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=03c9094e-1fb6-4cba-8da3-2628a967c4b5@intel.com \
--to=bhanuprakash.modem@intel.com \
--cc=I915-ci-infra@lists.freedesktop.org \
--cc=andrzej.hajda@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jari.tahvanainen@intel.com \
--cc=kamil.konieczny@linux.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