From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Juha-Pekka Heikkila" <juhapekka.heikkila@gmail.com>
Cc: igt-dev@lists.freedesktop.org
Subject: ✓ Xe.CI.BAT: success for Enable Vebox engine copy on Intel Xe driver (rev9)
Date: Fri, 20 Mar 2026 18:58:20 -0000 [thread overview]
Message-ID: <177403310050.382001.17186801078033123729@a3b018990fe9> (raw)
In-Reply-To: <20260320134611.876379-1-juhapekka.heikkila@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1486 bytes --]
== Series Details ==
Series: Enable Vebox engine copy on Intel Xe driver (rev9)
URL : https://patchwork.freedesktop.org/series/161376/
State : success
== Summary ==
CI Bug Log - changes from XEIGT_8815_BAT -> XEIGTPW_14827_BAT
====================================================
Summary
-------
**SUCCESS**
No regressions found.
Participating hosts (14 -> 14)
------------------------------
No changes in participating hosts
Known issues
------------
Here are the changes found in XEIGTPW_14827_BAT that come from known issues:
### IGT changes ###
#### Possible fixes ####
* igt@xe_waitfence@reltime:
- bat-dg2-oem2: [FAIL][1] ([Intel XE#6520]) -> [PASS][2]
[1]: https://intel-gfx-ci.01.org/tree/intel-xe/IGT_8815/bat-dg2-oem2/igt@xe_waitfence@reltime.html
[2]: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_14827/bat-dg2-oem2/igt@xe_waitfence@reltime.html
[Intel XE#6520]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/6520
Build changes
-------------
* IGT: IGT_8815 -> IGTPW_14827
* Linux: xe-4752-7535044a2418d22b59be0eb64af0353971f16bd8 -> xe-4754-f202c0d0dece0eeefb750a6a9d80f4b7442529f4
IGTPW_14827: 14827
IGT_8815: 8815
xe-4752-7535044a2418d22b59be0eb64af0353971f16bd8: 7535044a2418d22b59be0eb64af0353971f16bd8
xe-4754-f202c0d0dece0eeefb750a6a9d80f4b7442529f4: f202c0d0dece0eeefb750a6a9d80f4b7442529f4
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_14827/index.html
[-- Attachment #2: Type: text/html, Size: 2062 bytes --]
next prev parent reply other threads:[~2026-03-20 18:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 13:46 [PATCH i-g-t 0/8] Enable Vebox engine copy on Intel Xe driver Juha-Pekka Heikkila
2026-03-20 13:46 ` [PATCH i-g-t 1/8] lib: take out duplicate assert Juha-Pekka Heikkila
2026-03-20 13:46 ` [PATCH i-g-t 2/8] lib/intel_batchbuffer: make __intel_bb_create gt aware Juha-Pekka Heikkila
2026-03-20 13:46 ` [PATCH i-g-t 3/8] lib/xe: add xe_exec_queue_create_class_gt Juha-Pekka Heikkila
2026-03-20 13:46 ` [PATCH i-g-t 4/8] lib/intel_batchbuffer: add intel_bb_create_with_gt function Juha-Pekka Heikkila
2026-03-20 13:46 ` [PATCH i-g-t 5/8] lib/intel_batchbuffer: move engine class selection to helper Juha-Pekka Heikkila
2026-03-20 13:46 ` [PATCH i-g-t 6/8] lib/intel_batchbuffer/xe: add bb exec path to use specific engine and gt Juha-Pekka Heikkila
2026-03-20 13:46 ` [PATCH i-g-t 7/8] lib: Enable Vebox framebuffer copying on Intel Xe2 Juha-Pekka Heikkila
2026-03-20 13:46 ` [PATCH i-g-t 8/8] lib/igt_fb: on Intel Xe force Vebox copy on yuv formats Juha-Pekka Heikkila
2026-03-20 18:58 ` Patchwork [this message]
2026-03-20 19:15 ` ✓ i915.CI.BAT: success for Enable Vebox engine copy on Intel Xe driver (rev9) Patchwork
2026-03-21 12:06 ` ✗ i915.CI.Full: failure " Patchwork
2026-03-21 20:57 ` ✗ Xe.CI.FULL: " 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=177403310050.382001.17186801078033123729@a3b018990fe9 \
--to=patchwork@emeril.freedesktop.org \
--cc=igt-dev@lists.freedesktop.org \
--cc=juhapekka.heikkila@gmail.com \
/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