Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: intel-xe@lists.freedesktop.org
Subject: Re: ✗ Xe.CI.Full: failure for drm/xe/pf: Use correct function to check LMEM provisioning
Date: Fri, 20 Dec 2024 00:08:40 +0100	[thread overview]
Message-ID: <0843e016-b545-42ee-96e0-506e08f4eae0@intel.com> (raw)
In-Reply-To: <173442510904.3702663.621131809513776018@b555e5b46a47>



On 17.12.2024 09:45, Patchwork wrote:
> == Series Details ==
> 
> Series: drm/xe/pf: Use correct function to check LMEM provisioning
> URL   : https://patchwork.freedesktop.org/series/142678/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from xe-2386-49cc582754c205bbe43d4ef2b1fd3894bee1f3bd_full -> xe-pw-142678v1_full
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with xe-pw-142678v1_full absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in xe-pw-142678v1_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-142678v1_full:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####
> 

unrelated (change is PF specific)

>   * igt@kms_async_flips@async-flip-with-page-flip-events-atomic@pipe-c-hdmi-a-1-linear:
>     - shard-adlp:         [PASS][1] -> [DMESG-WARN][2]
>    [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2386-49cc582754c205bbe43d4ef2b1fd3894bee1f3bd/shard-adlp-2/igt@kms_async_flips@async-flip-with-page-flip-events-atomic@pipe-c-hdmi-a-1-linear.html
>    [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-142678v1/shard-adlp-1/igt@kms_async_flips@async-flip-with-page-flip-events-atomic@pipe-c-hdmi-a-1-linear.html
> 
>   * igt@kms_ccs@random-ccs-data-4-tiled-dg2-rc-ccs-cc@pipe-c-hdmi-a-6:
>     - shard-dg2-set2:     NOTRUN -> [INCOMPLETE][3]
>    [3]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-142678v1/shard-dg2-464/igt@kms_ccs@random-ccs-data-4-tiled-dg2-rc-ccs-cc@pipe-c-hdmi-a-6.html
> 
>   * igt@kms_flip@2x-plain-flip-fb-recreate@bc-hdmi-a6-dp4:
>     - shard-dg2-set2:     [PASS][4] -> [FAIL][5] +2 other tests fail
>    [4]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2386-49cc582754c205bbe43d4ef2b1fd3894bee1f3bd/shard-dg2-433/igt@kms_flip@2x-plain-flip-fb-recreate@bc-hdmi-a6-dp4.html
>    [5]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-142678v1/shard-dg2-433/igt@kms_flip@2x-plain-flip-fb-recreate@bc-hdmi-a6-dp4.html
> 
>   * igt@kms_pipe_crc_basic@suspend-read-crc@pipe-b-hdmi-a-3:
>     - shard-bmg:          [PASS][6] -> [FAIL][7] +3 other tests fail
>    [6]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2386-49cc582754c205bbe43d4ef2b1fd3894bee1f3bd/shard-bmg-4/igt@kms_pipe_crc_basic@suspend-read-crc@pipe-b-hdmi-a-3.html
>    [7]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-142678v1/shard-bmg-5/igt@kms_pipe_crc_basic@suspend-read-crc@pipe-b-hdmi-a-3.html
> 
>   * igt@xe_evict@evict-mixed-threads-large:
>     - shard-bmg:          NOTRUN -> [DMESG-FAIL][8]
>    [8]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-142678v1/shard-bmg-4/igt@xe_evict@evict-mixed-threads-large.html
> 
>   * igt@xe_pm@s3-mocs:
>     - shard-bmg:          [PASS][9] -> [INCOMPLETE][10]
>    [9]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2386-49cc582754c205bbe43d4ef2b1fd3894bee1f3bd/shard-bmg-7/igt@xe_pm@s3-mocs.html
>    [10]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-142678v1/shard-bmg-7/igt@xe_pm@s3-mocs.html
> 
>   * igt@xe_pm@s3-vm-bind-userptr:
>     - shard-bmg:          [PASS][11] -> [ABORT][12]
>    [11]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2386-49cc582754c205bbe43d4ef2b1fd3894bee1f3bd/shard-bmg-5/igt@xe_pm@s3-vm-bind-userptr.html
>    [12]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-142678v1/shard-bmg-3/igt@xe_pm@s3-vm-bind-userptr.html
> 
>   

  reply	other threads:[~2024-12-19 23:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-16 22:32 [PATCH] drm/xe/pf: Use correct function to check LMEM provisioning Michal Wajdeczko
2024-12-17  1:05 ` ✓ CI.Patch_applied: success for " Patchwork
2024-12-17  1:05 ` ✓ CI.checkpatch: " Patchwork
2024-12-17  1:06 ` ✓ CI.KUnit: " Patchwork
2024-12-17  1:24 ` ✓ CI.Build: " Patchwork
2024-12-17  1:26 ` ✓ CI.Hooks: " Patchwork
2024-12-17  1:28 ` ✓ CI.checksparse: " Patchwork
2024-12-17  1:57 ` ✓ Xe.CI.BAT: " Patchwork
2024-12-17  8:45 ` ✗ Xe.CI.Full: failure " Patchwork
2024-12-19 23:08   ` Michal Wajdeczko [this message]
2024-12-19  3:24 ` [PATCH] " Ghimiray, Himal Prasad

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=0843e016-b545-42ee-96e0-506e08f4eae0@intel.com \
    --to=michal.wajdeczko@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