From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: intel-xe@lists.freedesktop.org
Subject: Re: ✗ CI.BAT: failure for series starting with [1/2] drm/xe/guc: Use drm_device-managed version of mutex_init()
Date: Mon, 8 Apr 2024 11:19:02 +0200 [thread overview]
Message-ID: <8c1522cf-cc53-4b10-87a4-778ae7a9d968@intel.com> (raw)
In-Reply-To: <171241738524.1255282.14990289170083469257@8e613ede5ea5>
On 06.04.2024 17:29, Patchwork wrote:
> == Series Details ==
>
> Series: series starting with [1/2] drm/xe/guc: Use drm_device-managed version of mutex_init()
> URL : https://patchwork.freedesktop.org/series/132118/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from xe-1050-1bace689230323abe9cd3dfc6dd011fa5f9e6a05_BAT -> xe-pw-132118v1_BAT
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with xe-pw-132118v1_BAT absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in xe-pw-132118v1_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 (5 -> 5)
> ------------------------------
>
> No changes in participating hosts
>
> Possible new issues
> -------------------
>
> Here are the unknown changes that may have been introduced in xe-pw-132118v1_BAT:
>
> ### IGT changes ###
>
> #### Possible regressions ####
CI.FULL (no e-mail, dunno why) also reports some regression, but
reported GPF call stack points to xe_devcoredump_free() so it's unrelated
>
> * igt@xe_exec_compute_mode@twice-bindexecqueue-userptr-rebind:
> - bat-pvc-2: [PASS][1] -> [INCOMPLETE][2]
> [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-1050-1bace689230323abe9cd3dfc6dd011fa5f9e6a05/bat-pvc-2/igt@xe_exec_compute_mode@twice-bindexecqueue-userptr-rebind.html
> [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-132118v1/bat-pvc-2/igt@xe_exec_compute_mode@twice-bindexecqueue-userptr-rebind.html
also seems unrelated as series is touching cleanup phase that is common
to all platforms, not just PVC
>
>
> #### Suppressed ####
>
> The following results come from untrusted machines, tests, or statuses.
> They do not affect the overall result.
>
> * igt@kms_flip@basic-flip-vs-wf_vblank@c-edp1:
> - {bat-lnl-1}: [PASS][3] -> [FAIL][4] +1 other test fail
> [3]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-1050-1bace689230323abe9cd3dfc6dd011fa5f9e6a05/bat-lnl-1/igt@kms_flip@basic-flip-vs-wf_vblank@c-edp1.html
> [4]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-132118v1/bat-lnl-1/igt@kms_flip@basic-flip-vs-wf_vblank@c-edp1.html
>
>
> {name}: This element is suppressed. This means it is ignored when computing
> the status of the difference (SUCCESS, WARNING, or FAILURE).
>
>
>
> Build changes
> -------------
>
> * Linux: xe-1050-1bace689230323abe9cd3dfc6dd011fa5f9e6a05 -> xe-pw-132118v1
>
> IGT_7801: 7801
> xe-1050-1bace689230323abe9cd3dfc6dd011fa5f9e6a05: 1bace689230323abe9cd3dfc6dd011fa5f9e6a05
> xe-pw-132118v1: 132118v1
>
> == Logs ==
>
> For more details see: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-132118v1/index.html
>
next prev parent reply other threads:[~2024-04-08 9:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-06 14:39 [PATCH 1/2] drm/xe/guc: Use drm_device-managed version of mutex_init() Michal Wajdeczko
2024-04-06 14:39 ` [PATCH 2/2] drm/xe/guc: Initialize GuC ID manager sooner Michal Wajdeczko
2024-04-06 18:24 ` Matthew Brost
2024-04-06 14:46 ` ✓ CI.Patch_applied: success for series starting with [1/2] drm/xe/guc: Use drm_device-managed version of mutex_init() Patchwork
2024-04-06 14:46 ` ✓ CI.checkpatch: " Patchwork
2024-04-06 14:47 ` ✓ CI.KUnit: " Patchwork
2024-04-06 14:58 ` ✓ CI.Build: " Patchwork
2024-04-06 15:01 ` ✓ CI.Hooks: " Patchwork
2024-04-06 15:02 ` ✓ CI.checksparse: " Patchwork
2024-04-06 15:29 ` ✗ CI.BAT: failure " Patchwork
2024-04-08 9:19 ` Michal Wajdeczko [this message]
2024-04-06 18:23 ` [PATCH 1/2] " 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=8c1522cf-cc53-4b10-87a4-778ae7a9d968@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