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: ✓ CI.BAT: success for More VF tweaks
Date: Mon, 8 Apr 2024 14:32:02 +0200	[thread overview]
Message-ID: <187fffc9-1a7c-41ab-9a0b-34df27f446d9@intel.com> (raw)
In-Reply-To: <171233678227.1239329.13976834407139235427@8e613ede5ea5>



On 05.04.2024 19:06, Patchwork wrote:
> == Series Details ==
> 
> Series: More VF tweaks
> URL   : https://patchwork.freedesktop.org/series/132080/
> State : success
> 
> == Summary ==
> 
> CI Bug Log - changes from xe-1046-5714711c6612120bd9c306824ec807d322c0735b_BAT -> xe-pw-132080v1_BAT
> ====================================================
> 
> Summary
> -------
> 
>   **SUCCESS**
> 
>   No regressions found.
> 

CI.FULL complains about
igt@kms_flip@single-buffer-flip-vs-dpms-off-vs-modeset@b-hdmi-a2 on ADLP
but that is unrelated to this series

>   
> 
> Participating hosts (5 -> 5)
> ------------------------------
> 
>   No changes in participating hosts
> 
> Known issues
> ------------
> 
>   Here are the changes found in xe-pw-132080v1_BAT that come from known issues:
> 
> ### IGT changes ###
> 
> #### Issues hit ####
> 
>   * igt@xe_evict@evict-beng-small-external:
>     - bat-pvc-2:          NOTRUN -> [FAIL][1] ([Intel XE#1000]) +3 other tests fail
>    [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-132080v1/bat-pvc-2/igt@xe_evict@evict-beng-small-external.html
> 
>   * igt@xe_evict@evict-small-cm:
>     - bat-adlp-7:         NOTRUN -> [SKIP][2] ([Intel XE#261] / [Intel XE#688]) +15 other tests skip
>    [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-132080v1/bat-adlp-7/igt@xe_evict@evict-small-cm.html
> 
>   * igt@xe_evict@evict-small-external-cm:
>     - bat-pvc-2:          NOTRUN -> [DMESG-FAIL][3] ([Intel XE#482]) +3 other tests dmesg-fail
>    [3]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-132080v1/bat-pvc-2/igt@xe_evict@evict-small-external-cm.html
> 
>   
>   {name}: This element is suppressed. This means it is ignored when computing
>           the status of the difference (SUCCESS, WARNING, or FAILURE).
> 
>   [Intel XE#1000]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1000
>   [Intel XE#1442]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1442
>   [Intel XE#1462]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1462
>   [Intel XE#261]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/261
>   [Intel XE#482]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/482
>   [Intel XE#688]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/688
> 
> 
> Build changes
> -------------
> 
>   * IGT: IGT_7800 -> IGT_7801
>   * Linux: xe-1046-5714711c6612120bd9c306824ec807d322c0735b -> xe-pw-132080v1
> 
>   IGT_7800: 7800
>   IGT_7801: 7801
>   xe-1046-5714711c6612120bd9c306824ec807d322c0735b: 5714711c6612120bd9c306824ec807d322c0735b
>   xe-pw-132080v1: 132080v1
> 
> == Logs ==
> 
> For more details see: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-132080v1/index.html
> 

      reply	other threads:[~2024-04-08 12:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-05 13:39 [PATCH 0/3] More VF tweaks Michal Wajdeczko
2024-04-05 13:39 ` [PATCH 1/3] drm/xe/vf: Don't emit access to Global HWSP if VF Michal Wajdeczko
2024-04-08 11:19   ` Piotr Piórkowski
2024-04-05 13:39 ` [PATCH 2/3] drm/xe/vf: Don't try to program MOCS " Michal Wajdeczko
2024-04-08  6:02   ` Ghimiray, Himal Prasad
2024-04-05 13:39 ` [PATCH 3/3] drm/xe/vf: Don't try to read legacy GuC MMIO notification " Michal Wajdeczko
2024-04-08  6:03   ` Ghimiray, Himal Prasad
2024-04-05 16:09 ` ✓ CI.Patch_applied: success for More VF tweaks Patchwork
2024-04-05 16:10 ` ✓ CI.checkpatch: " Patchwork
2024-04-05 16:12 ` ✓ CI.KUnit: " Patchwork
2024-04-05 16:24 ` ✓ CI.Build: " Patchwork
2024-04-05 16:27 ` ✓ CI.Hooks: " Patchwork
2024-04-05 16:29 ` ✓ CI.checksparse: " Patchwork
2024-04-05 17:06 ` ✓ CI.BAT: " Patchwork
2024-04-08 12:32   ` Michal Wajdeczko [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=187fffc9-1a7c-41ab-9a0b-34df27f446d9@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