From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: intel-xe@lists.freedesktop.org
Subject: Re: ✗ CI.BAT: failure for Introduce GuC context ID Manager
Date: Thu, 11 Jan 2024 21:30:29 +0100 [thread overview]
Message-ID: <911c1338-24d0-499f-84c5-40983fd2dcee@intel.com> (raw)
In-Reply-To: <170492736329.270358.9755170133663410009@5338d5abeb45>
On 10.01.2024 23:56, Patchwork wrote:
> == Series Details ==
>
> Series: Introduce GuC context ID Manager
> URL : https://patchwork.freedesktop.org/series/128445/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from xe-614-bb9e8031d2feb59becdea41e54e62f1bc47f3ef9_BAT -> xe-pw-128445v1_BAT
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with xe-pw-128445v1_BAT absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in xe-pw-128445v1_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-128445v1_BAT:
>
> ### IGT changes ###
>
> #### Possible regressions ####
>
> * igt@xe_exec_fault_mode@twice-bindexecqueue-userptr-imm:
> - bat-pvc-2: [PASS][1] -> [INCOMPLETE][2]
> [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-614-bb9e8031d2feb59becdea41e54e62f1bc47f3ef9/bat-pvc-2/igt@xe_exec_fault_mode@twice-bindexecqueue-userptr-imm.html
> [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-128445v1/bat-pvc-2/igt@xe_exec_fault_mode@twice-bindexecqueue-userptr-imm.html
doesn't look like a real regression
these "exec...twice" tests doesn't seem stable (seen similar
"regressions" on other unrelated series)
>
>
> Known issues
> ------------
>
> Here are the changes found in xe-pw-128445v1_BAT that come from known issues:
>
> ### IGT changes ###
>
> #### Issues hit ####
>
> * igt@kms_flip@basic-flip-vs-wf_vblank@d-edp1:
> - bat-adlp-7: [PASS][3] -> [FAIL][4] ([Intel XE#480])
> [3]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-614-bb9e8031d2feb59becdea41e54e62f1bc47f3ef9/bat-adlp-7/igt@kms_flip@basic-flip-vs-wf_vblank@d-edp1.html
> [4]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-128445v1/bat-adlp-7/igt@kms_flip@basic-flip-vs-wf_vblank@d-edp1.html
>
>
> #### Possible fixes ####
>
> * igt@kms_flip@basic-flip-vs-wf_vblank@c-edp1:
> - bat-adlp-7: [FAIL][5] ([Intel XE#480]) -> [PASS][6]
> [5]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-614-bb9e8031d2feb59becdea41e54e62f1bc47f3ef9/bat-adlp-7/igt@kms_flip@basic-flip-vs-wf_vblank@c-edp1.html
> [6]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-128445v1/bat-adlp-7/igt@kms_flip@basic-flip-vs-wf_vblank@c-edp1.html
>
> * igt@kms_flip@basic-flip-vs-wf_vblank@d-dp3:
> - bat-dg2-oem2: [FAIL][7] ([Intel XE#480]) -> [PASS][8] +1 other test pass
> [7]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-614-bb9e8031d2feb59becdea41e54e62f1bc47f3ef9/bat-dg2-oem2/igt@kms_flip@basic-flip-vs-wf_vblank@d-dp3.html
> [8]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-128445v1/bat-dg2-oem2/igt@kms_flip@basic-flip-vs-wf_vblank@d-dp3.html
>
>
> [Intel XE#480]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/480
>
>
> Build changes
> -------------
>
> * IGT: IGT_7667 -> IGT_7668
> * Linux: xe-614-bb9e8031d2feb59becdea41e54e62f1bc47f3ef9 -> xe-pw-128445v1
>
> IGT_7667: e9b26a2f44a6b1125b36a77ed8366cb82b502622 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
> IGT_7668: 3f2879fef93c0c546a2f1c0aa48a9cc2a594b9d2 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
> xe-614-bb9e8031d2feb59becdea41e54e62f1bc47f3ef9: bb9e8031d2feb59becdea41e54e62f1bc47f3ef9
> xe-pw-128445v1: 128445v1
>
> == Logs ==
>
> For more details see: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-128445v1/index.html
>
prev parent reply other threads:[~2024-01-11 20:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 17:46 [PATCH 0/4] Introduce GuC context ID Manager Michal Wajdeczko
2024-01-10 17:46 ` [PATCH 1/4] drm/xe/guc: Move GUC_ID_MAX definition to GuC ABI header Michal Wajdeczko
2024-01-22 3:15 ` Matthew Brost
2024-01-10 17:46 ` [PATCH 2/4] drm/xe/guc: Introduce GuC context ID Manager Michal Wajdeczko
2024-01-22 3:53 ` Matthew Brost
2024-03-13 22:09 ` Michal Wajdeczko
2024-01-10 17:46 ` [PATCH 3/4] drm/xe/kunit: Add basic tests for " Michal Wajdeczko
2024-01-10 17:46 ` [PATCH 4/4] drm/xe/guc: Use GuC ID Manager in submission code Michal Wajdeczko
2024-01-22 4:10 ` Matthew Brost
2024-01-10 22:08 ` ✓ CI.Patch_applied: success for Introduce GuC context ID Manager Patchwork
2024-01-10 22:09 ` ✗ CI.checkpatch: warning " Patchwork
2024-01-10 22:10 ` ✓ CI.KUnit: success " Patchwork
2024-01-10 22:17 ` ✓ CI.Build: " Patchwork
2024-01-10 22:18 ` ✓ CI.Hooks: " Patchwork
2024-01-10 22:19 ` ✓ CI.checksparse: " Patchwork
2024-01-10 22:56 ` ✗ CI.BAT: failure " Patchwork
2024-01-11 20:30 ` 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=911c1338-24d0-499f-84c5-40983fd2dcee@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