From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: intel-xe@lists.freedesktop.org, I915-ci-infra@lists.freedesktop.org
Subject: Re: ✗ Xe.CI.Full: failure for drm/xe/guc: Fix sizeof(32) typo
Date: Tue, 21 Jan 2025 21:45:03 +0100 [thread overview]
Message-ID: <d662849e-a3cc-4f68-a581-9b567a9f195a@intel.com> (raw)
In-Reply-To: <173747831846.2649833.5021404524478257751@b555e5b46a47>
On 21.01.2025 17:51, Patchwork wrote:
> == Series Details ==
>
> Series: drm/xe/guc: Fix sizeof(32) typo
> URL : https://patchwork.freedesktop.org/series/143787/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from xe-2518-bb123c6e757601d42f71952d879b35f97472d56b_full -> xe-pw-143787v1_full
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with xe-pw-143787v1_full absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in xe-pw-143787v1_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-143787v1_full:
>
> ### IGT changes ###
>
> #### Possible regressions ####
>
> * igt@kms_async_flips@crc:
> - shard-bmg: [PASS][1] -> [INCOMPLETE][2] +1 other test incomplete
> [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2518-bb123c6e757601d42f71952d879b35f97472d56b/shard-bmg-8/igt@kms_async_flips@crc.html
> [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143787v1/shard-bmg-7/igt@kms_async_flips@crc.html
> - shard-dg2-set2: [PASS][3] -> [INCOMPLETE][4] +1 other test incomplete
> [3]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2518-bb123c6e757601d42f71952d879b35f97472d56b/shard-dg2-435/igt@kms_async_flips@crc.html
> [4]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143787v1/shard-dg2-463/igt@kms_async_flips@crc.html
>
> * igt@kms_atomic@plane-primary-legacy@pipe-a-dp-2:
> - shard-bmg: NOTRUN -> [DMESG-WARN][5] +1 other test dmesg-warn
> [5]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143787v1/shard-bmg-1/igt@kms_atomic@plane-primary-legacy@pipe-a-dp-2.html
>
> * igt@kms_flip@flip-vs-suspend-interruptible@a-edp1:
> - shard-lnl: [PASS][6] -> [FAIL][7]
> [6]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2518-bb123c6e757601d42f71952d879b35f97472d56b/shard-lnl-3/igt@kms_flip@flip-vs-suspend-interruptible@a-edp1.html
> [7]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143787v1/shard-lnl-7/igt@kms_flip@flip-vs-suspend-interruptible@a-edp1.html
>
> * igt@kms_flip@wf_vblank-ts-check@b-hdmi-a1:
> - shard-adlp: [PASS][8] -> [FAIL][9]
> [8]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2518-bb123c6e757601d42f71952d879b35f97472d56b/shard-adlp-2/igt@kms_flip@wf_vblank-ts-check@b-hdmi-a1.html
> [9]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143787v1/shard-adlp-9/igt@kms_flip@wf_vblank-ts-check@b-hdmi-a1.html
>
> * igt@kms_frontbuffer_tracking@fbc-1p-rte:
> - shard-bmg: NOTRUN -> [SKIP][10]
> [10]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143787v1/shard-bmg-3/igt@kms_frontbuffer_tracking@fbc-1p-rte.html
>
> * igt@kms_plane_multiple@tiling-none:
> - shard-bmg: [PASS][11] -> [DMESG-WARN][12] +22 other tests dmesg-warn
> [11]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2518-bb123c6e757601d42f71952d879b35f97472d56b/shard-bmg-2/igt@kms_plane_multiple@tiling-none.html
> [12]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143787v1/shard-bmg-1/igt@kms_plane_multiple@tiling-none.html
>
> * igt@kms_plane_scaling@plane-upscale-20x20-with-modifiers:
> - shard-adlp: [PASS][13] -> [DMESG-WARN][14] +4 other tests dmesg-warn
> [13]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2518-bb123c6e757601d42f71952d879b35f97472d56b/shard-adlp-9/igt@kms_plane_scaling@plane-upscale-20x20-with-modifiers.html
> [14]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143787v1/shard-adlp-8/igt@kms_plane_scaling@plane-upscale-20x20-with-modifiers.html
>
all KMS
all unrelated
next prev parent reply other threads:[~2025-01-21 20:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-21 9:48 [PATCH] drm/xe/guc: Fix sizeof(32) typo Michal Wajdeczko
2025-01-21 11:54 ` ✓ CI.Patch_applied: success for " Patchwork
2025-01-21 11:55 ` ✓ CI.checkpatch: " Patchwork
2025-01-21 11:56 ` ✓ CI.KUnit: " Patchwork
2025-01-21 12:12 ` ✓ CI.Build: " Patchwork
2025-01-21 12:14 ` ✓ CI.Hooks: " Patchwork
2025-01-21 12:16 ` ✓ CI.checksparse: " Patchwork
2025-01-21 12:42 ` ✓ Xe.CI.BAT: " Patchwork
2025-01-21 16:51 ` ✗ Xe.CI.Full: failure " Patchwork
2025-01-21 20:45 ` Michal Wajdeczko [this message]
2025-01-21 17:39 ` [PATCH] " Summers, Stuart
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=d662849e-a3cc-4f68-a581-9b567a9f195a@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=I915-ci-infra@lists.freedesktop.org \
--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