From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: <intel-xe@lists.freedesktop.org>
Subject: Re: ✗ Xe.CI.FULL: failure for Some more _types.h cleanups (rev4)
Date: Thu, 5 Feb 2026 21:07:42 +0100 [thread overview]
Message-ID: <324eeef3-47c2-443e-9aee-2cc932c26fea@intel.com> (raw)
In-Reply-To: <177030162507.228151.7216687703707281185@a3b018990fe9>
On 2/5/2026 3:27 PM, Patchwork wrote:
> *Patch Details*
> *Series:* Some more _types.h cleanups (rev4)
> *URL:* https://patchwork.freedesktop.org/series/149807/ <https://patchwork.freedesktop.org/series/149807/>
> *State:* failure
> *Details:* https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-149807v4/index.html <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-149807v4/index.html>
>
>
> CI Bug Log - changes from xe-4500-55e3e3aeecf80d9fd2536acd8ed785282be5a7b3_FULL -> xe-pw-149807v4_FULL
>
>
> Summary
>
> *FAILURE*
>
> Serious unknown changes coming with xe-pw-149807v4_FULL absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in xe-pw-149807v4_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 (2 -> 2)
>
> No changes in participating hosts
>
>
> Possible new issues
>
> Here are the unknown changes that may have been introduced in xe-pw-149807v4_FULL:
>
>
> IGT changes
>
>
> Possible regressions
>
> * igt@kms_flip@2x-flip-vs-expired-vblank-interruptible@ab-dp2-hdmi-a3:
> o shard-bmg: PASS <https://intel-gfx-ci.01.org/tree/intel-xe/xe-4500-55e3e3aeecf80d9fd2536acd8ed785282be5a7b3/shard-bmg-8/igt@kms_flip@2x-flip-vs-expired-vblank-interruptible@ab-dp2-hdmi-a3.html> -> FAIL <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-149807v4/shard-bmg-2/igt@kms_flip@2x-flip-vs-expired-vblank-interruptible@ab-dp2-hdmi-a3.html>
unrelated
(kms_flip:7788) CRITICAL: Test assertion failure function run_test_step, file ../tests/kms_flip.c:928:
(kms_flip:7788) CRITICAL: Failed assertion: end - start < 500
(kms_flip:7788) CRITICAL: Last errno: 4, Interrupted system call
prev parent reply other threads:[~2026-02-05 20:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 21:12 [PATCH v2 0/4] Some more _types.h cleanups Michal Wajdeczko
2026-02-03 21:12 ` [PATCH v2 1/4] drm/xe: Move xe_root_tile_mmio() to xe_device.h Michal Wajdeczko
2026-02-03 21:12 ` [PATCH v2 2/4] drm/xe: Promote struct xe_mmio definition to own file Michal Wajdeczko
2026-02-03 21:12 ` [PATCH v2 3/4] drm/xe: Promote struct xe_tile " Michal Wajdeczko
2026-02-03 23:47 ` Matt Roper
2026-02-03 21:12 ` [PATCH v2 4/4] drm/xe: Drop unnecessary include from xe_tile.h Michal Wajdeczko
2026-02-03 21:52 ` ✗ CI.checkpatch: warning for Some more _types.h cleanups (rev3) Patchwork
2026-02-03 21:53 ` ✓ CI.KUnit: success " Patchwork
2026-02-03 22:26 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-02-04 12:36 ` ✗ Xe.CI.FULL: " Patchwork
2026-02-04 23:29 ` ✗ CI.checkpatch: warning for Some more _types.h cleanups (rev4) Patchwork
2026-02-04 23:31 ` ✓ CI.KUnit: success " Patchwork
2026-02-05 0:04 ` ✓ Xe.CI.BAT: " Patchwork
2026-02-05 14:27 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-02-05 20:07 ` 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=324eeef3-47c2-443e-9aee-2cc932c26fea@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