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/vf: Fix signature of print functions
Date: Fri, 15 May 2026 15:52:08 +0200	[thread overview]
Message-ID: <ccec0071-5a99-4822-9344-96b79d987673@intel.com> (raw)
In-Reply-To: <177884599193.75062.4714606030804476512@5ab824fced77>



On 5/15/2026 1:53 PM, Patchwork wrote:
> *Patch Details*
> *Series:*	drm/xe/vf: Fix signature of print functions
> *URL:*	https://patchwork.freedesktop.org/series/166583/ <https://patchwork.freedesktop.org/series/166583/>
> *State:*	failure
> *Details:*	https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-166583v1/index.html <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-166583v1/index.html>
> 
> 
>   CI Bug Log - changes from xe-5063-121c16f9d8c56ea07263df84ab971cc10870fe88_FULL -> xe-pw-166583v1_FULL
> 
> 
>     Summary
> 
> *FAILURE*
> 
> Serious unknown changes coming with xe-pw-166583v1_FULL absolutely need to be
> verified manually.
> 
> If you think the reported changes have nothing to do with the changes
> introduced in xe-pw-166583v1_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 (2 -> 2)
> 
> No changes in participating hosts
> 
> 
>     Possible new issues
> 
> Here are the unknown changes that may have been introduced in xe-pw-166583v1_FULL:
> 
> 
>       IGT changes
> 
> 
>         Possible regressions
> 
>   * igt@xe_module_load@reload:
>       o shard-bmg: PASS <https://intel-gfx-ci.01.org/tree/intel-xe/xe-5063-121c16f9d8c56ea07263df84ab971cc10870fe88/shard-bmg-8/igt@xe_module_load@reload.html> -> DMESG-WARN <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-166583v1/shard-bmg-2/igt@xe_module_load@reload.html>

unrelated

<4> [152.912942] xe 0000:03:00.0: [drm] Tile0: GT1: GuC not ready after disabling idle flow (GUC_STATUS: 0x800370ec)



      reply	other threads:[~2026-05-15 13:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-14 15:57 [PATCH] drm/xe/vf: Fix signature of print functions Michal Wajdeczko
2026-05-14 16:24 ` ✓ CI.KUnit: success for " Patchwork
2026-05-14 16:42 ` [PATCH] " Lin, Shuicheng
2026-05-14 17:27 ` ✓ Xe.CI.BAT: success for " Patchwork
2026-05-15  9:53 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-05-15 11:53 ` Patchwork
2026-05-15 13:52   ` 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=ccec0071-5a99-4822-9344-96b79d987673@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