From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Francois Dugast" <francois.dugast@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: ✗ Xe.CI.BAT: failure for gpu/buddy: Per-order free and used block scoreboards (rev2)
Date: Tue, 12 May 2026 01:05:00 -0000 [thread overview]
Message-ID: <177854790053.58917.11671886231681330321@5ab824fced77> (raw)
In-Reply-To: <20260511164217.150237-1-francois.dugast@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1787 bytes --]
== Series Details ==
Series: gpu/buddy: Per-order free and used block scoreboards (rev2)
URL : https://patchwork.freedesktop.org/series/165914/
State : failure
== Summary ==
CI Bug Log - changes from xe-5042-311a7de0a4e360124ba1abb933df42b021ef8b9d_BAT -> xe-pw-165914v2_BAT
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with xe-pw-165914v2_BAT absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in xe-pw-165914v2_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 (13 -> 13)
------------------------------
No changes in participating hosts
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in xe-pw-165914v2_BAT:
### IGT changes ###
#### Possible regressions ####
* igt@xe_waitfence@reltime:
- bat-ptl-1: [PASS][1] -> [FAIL][2]
[1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-5042-311a7de0a4e360124ba1abb933df42b021ef8b9d/bat-ptl-1/igt@xe_waitfence@reltime.html
[2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-165914v2/bat-ptl-1/igt@xe_waitfence@reltime.html
Build changes
-------------
* Linux: xe-5042-311a7de0a4e360124ba1abb933df42b021ef8b9d -> xe-pw-165914v2
IGT_8903: 6f88532e2fe22529195cc2f8cabff93d994688f8 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
xe-5042-311a7de0a4e360124ba1abb933df42b021ef8b9d: 311a7de0a4e360124ba1abb933df42b021ef8b9d
xe-pw-165914v2: 165914v2
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-165914v2/index.html
[-- Attachment #2: Type: text/html, Size: 2372 bytes --]
next prev parent reply other threads:[~2026-05-12 1:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 16:41 [PATCH v2 0/3] gpu/buddy: Per-order free and used block scoreboards Francois Dugast
2026-05-11 16:41 ` [PATCH v2 1/3] gpu/buddy: Fix use-after-free in split_block() call sites Francois Dugast
2026-05-11 16:41 ` [PATCH v2 2/3] gpu/buddy: Track per-order free blocks with a scoreboard Francois Dugast
2026-05-15 15:50 ` Matthew Auld
2026-05-11 16:41 ` [PATCH v2 3/3] gpu/buddy: Track per-order used " Francois Dugast
2026-05-11 23:29 ` ✗ CI.checkpatch: warning for gpu/buddy: Per-order free and used block scoreboards (rev2) Patchwork
2026-05-11 23:30 ` ✓ CI.KUnit: success " Patchwork
2026-05-12 1:05 ` Patchwork [this message]
2026-05-12 4:13 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-05-12 12:33 ` ✗ CI.checkpatch: warning for gpu/buddy: Per-order free and used block scoreboards (rev3) Patchwork
2026-05-12 12:34 ` ✓ CI.KUnit: success " Patchwork
2026-05-12 13:57 ` ✓ Xe.CI.BAT: " Patchwork
2026-05-13 0:43 ` ✗ Xe.CI.FULL: failure " Patchwork
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=177854790053.58917.11671886231681330321@5ab824fced77 \
--to=patchwork@emeril.freedesktop.org \
--cc=francois.dugast@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).