From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: intel-xe@lists.freedesktop.org
Subject: Re: ✗ CI.FULL: failure for drm/xe: Add memirq report page address helpers
Date: Mon, 30 Sep 2024 21:41:02 +0200 [thread overview]
Message-ID: <069c2ca4-79b8-4d1e-a42f-9758e7e588cf@intel.com> (raw)
In-Reply-To: <172741931040.1109838.104412298661228358@2413ebb6fbb6>
On 27.09.2024 08:41, Patchwork wrote:
> == Series Details ==
>
> Series: drm/xe: Add memirq report page address helpers
> URL : https://patchwork.freedesktop.org/series/139084/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from xe-1978-6b498b1015e38b1b7dbd1c7e3ab0a9be5d48f4da_full -> xe-pw-139084v1_full
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with xe-pw-139084v1_full absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in xe-pw-139084v1_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 (4 -> 4)
> ------------------------------
>
> No changes in participating hosts
>
> Possible new issues
> -------------------
>
> Here are the unknown changes that may have been introduced in xe-pw-139084v1_full:
>
> ### IGT changes ###
>
> #### Possible regressions ####
unrelated, patch is MEMIRQ specific, which is now applicable to VF only
>
> * igt@kms_ccs@random-ccs-data-4-tiled-dg2-rc-ccs-cc:
> - shard-dg2-set2: [PASS][1] -> [INCOMPLETE][2] +1 other test incomplete
> [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-1978-6b498b1015e38b1b7dbd1c7e3ab0a9be5d48f4da/shard-dg2-434/igt@kms_ccs@random-ccs-data-4-tiled-dg2-rc-ccs-cc.html
> [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-139084v1/shard-dg2-432/igt@kms_ccs@random-ccs-data-4-tiled-dg2-rc-ccs-cc.html
>
> * igt@kms_cursor_crc@cursor-offscreen-128x128:
> - shard-lnl: [PASS][3] -> [DMESG-WARN][4] +1 other test dmesg-warn
> [3]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-1978-6b498b1015e38b1b7dbd1c7e3ab0a9be5d48f4da/shard-lnl-7/igt@kms_cursor_crc@cursor-offscreen-128x128.html
> [4]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-139084v1/shard-lnl-3/igt@kms_cursor_crc@cursor-offscreen-128x128.html
>
> * igt@kms_plane_scaling@intel-max-src-size@pipe-a-dp-4:
> - shard-dg2-set2: [PASS][5] -> [FAIL][6] +1 other test fail
> [5]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-1978-6b498b1015e38b1b7dbd1c7e3ab0a9be5d48f4da/shard-dg2-463/igt@kms_plane_scaling@intel-max-src-size@pipe-a-dp-4.html
> [6]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-139084v1/shard-dg2-463/igt@kms_plane_scaling@intel-max-src-size@pipe-a-dp-4.html
>
>
> #### Warnings ####
>
> * igt@xe_exec_fault_mode@many-execqueues-userptr-invalidate-race-prefetch:
> - shard-dg2-set2: [SKIP][7] ([Intel XE#1201]) -> [SKIP][8] +4 other tests skip
> [7]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-1978-6b498b1015e38b1b7dbd1c7e3ab0a9be5d48f4da/shard-dg2-434/igt@xe_exec_fault_mode@many-execqueues-userptr-invalidate-race-prefetch.html
> [8]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-139084v1/shard-dg2-432/igt@xe_exec_fault_mode@many-execqueues-userptr-invalidate-race-prefetch.html
>
>
prev parent reply other threads:[~2024-09-30 19:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-25 8:44 [PATCH] drm/xe: Add memirq report page address helpers Michal Wajdeczko
2024-09-25 9:35 ` Ilia Levi
2024-09-26 11:27 ` ✓ CI.Patch_applied: success for " Patchwork
2024-09-26 11:27 ` ✓ CI.checkpatch: " Patchwork
2024-09-26 11:28 ` ✓ CI.KUnit: " Patchwork
2024-09-26 11:40 ` ✓ CI.Build: " Patchwork
2024-09-26 11:42 ` ✓ CI.Hooks: " Patchwork
2024-09-26 11:44 ` ✓ CI.checksparse: " Patchwork
2024-09-26 12:29 ` ✓ CI.BAT: " Patchwork
2024-09-27 6:41 ` ✗ CI.FULL: failure " Patchwork
2024-09-30 19:41 ` 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=069c2ca4-79b8-4d1e-a42f-9758e7e588cf@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