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: failure for drm/xe/guc: Return CTB response length
Date: Thu, 11 Jan 2024 18:31:51 +0100	[thread overview]
Message-ID: <d8663aac-8071-424b-afc8-88efd23a90a6@intel.com> (raw)
In-Reply-To: <170498982314.290001.7423231611964465904@5338d5abeb45>



On 11.01.2024 17:17, Patchwork wrote:
> == Series Details ==
> 
> Series: drm/xe/guc: Return CTB response length
> URL   : https://patchwork.freedesktop.org/series/128675/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from xe-618-79184e72263e91528195db01783148435c7e4fad_BAT -> xe-pw-128675v1_BAT
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with xe-pw-128675v1_BAT absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in xe-pw-128675v1_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 -> 4)
> ------------------------------
> 
>   No changes in participating hosts
> 
> Possible new issues
> -------------------
> 
>   Here are the unknown changes that may have been introduced in xe-pw-128675v1_BAT:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####
> 
>   * igt@xe_exec_fault_mode@twice-basic-prefetch:
>     - bat-pvc-2:          NOTRUN -> [INCOMPLETE][1]
>    [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-128675v1/bat-pvc-2/igt@xe_exec_fault_mode@twice-basic-prefetch.html

"This test didn't produce any output. The machine probably rebooted
ungracefully."

and it's not that uncommon
anyway, it seems unrelated

> 
>   
> Known issues
> ------------
> 
>   Here are the changes found in xe-pw-128675v1_BAT that come from known issues:
> 
> ### IGT changes ###
> 
> #### Issues hit ####
> 
>   * igt@xe_exec_fault_mode@twice-bindexecqueue-userptr-prefetch:
>     - bat-atsm-2:         NOTRUN -> [SKIP][2] ([Intel XE#288]) +6 other tests skip
>    [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-128675v1/bat-atsm-2/igt@xe_exec_fault_mode@twice-bindexecqueue-userptr-prefetch.html
> 
>   
> #### Possible fixes ####
> 
>   * igt@kms_frontbuffer_tracking@basic:
>     - bat-adlp-7:         [DMESG-FAIL][3] ([Intel XE#1033]) -> [PASS][4]
>    [3]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-618-79184e72263e91528195db01783148435c7e4fad/bat-adlp-7/igt@kms_frontbuffer_tracking@basic.html
>    [4]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-128675v1/bat-adlp-7/igt@kms_frontbuffer_tracking@basic.html
> 
>   * igt@xe_create@create-execqueues-noleak:
>     - bat-atsm-2:         [FAIL][5] ([Intel XE#1099]) -> [PASS][6]
>    [5]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-618-79184e72263e91528195db01783148435c7e4fad/bat-atsm-2/igt@xe_create@create-execqueues-noleak.html
>    [6]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-128675v1/bat-atsm-2/igt@xe_create@create-execqueues-noleak.html
> 
>   
> #### Warnings ####
> 
>   * igt@xe_exec_fault_mode@twice-userptr-invalidate-prefetch:
>     - bat-atsm-2:         [INCOMPLETE][7] ([Intel XE#506]) -> [SKIP][8] ([Intel XE#288])
>    [7]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-618-79184e72263e91528195db01783148435c7e4fad/bat-atsm-2/igt@xe_exec_fault_mode@twice-userptr-invalidate-prefetch.html
>    [8]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-128675v1/bat-atsm-2/igt@xe_exec_fault_mode@twice-userptr-invalidate-prefetch.html
> 
>   
>   [Intel XE#1033]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1033
>   [Intel XE#1099]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1099
>   [Intel XE#288]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/288
>   [Intel XE#506]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/506
> 
> 
> Build changes
> -------------
> 
>   * IGT: IGT_7669 -> IGT_7670
>   * Linux: xe-618-79184e72263e91528195db01783148435c7e4fad -> xe-pw-128675v1
> 
>   IGT_7669: 418064e40ca6399700b0548983fdb679be4d855b @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
>   IGT_7670: 1b32bcdb2d9965090234739aba891a90743e01c4 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
>   xe-618-79184e72263e91528195db01783148435c7e4fad: 79184e72263e91528195db01783148435c7e4fad
>   xe-pw-128675v1: 128675v1
> 
> == Logs ==
> 
> For more details see: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-128675v1/index.html
> 

  reply	other threads:[~2024-01-11 17:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-11 15:27 [PATCH] drm/xe/guc: Return CTB response length Michal Wajdeczko
2024-01-11 15:30 ` ✓ CI.Patch_applied: success for " Patchwork
2024-01-11 15:30 ` ✓ CI.checkpatch: " Patchwork
2024-01-11 15:31 ` ✓ CI.KUnit: " Patchwork
2024-01-11 15:38 ` ✓ CI.Build: " Patchwork
2024-01-11 15:39 ` ✓ CI.Hooks: " Patchwork
2024-01-11 15:40 ` ✓ CI.checksparse: " Patchwork
2024-01-11 16:17 ` ✗ CI.BAT: failure " Patchwork
2024-01-11 17:31   ` Michal Wajdeczko [this message]
2024-01-11 16:40 ` [PATCH] " Matthew Brost
2024-01-11 17:07   ` Michal Wajdeczko
2024-01-11 20:02     ` Matthew Brost

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=d8663aac-8071-424b-afc8-88efd23a90a6@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