From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Matthew Brost" <matthew.brost@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: ✓ CI.BAT: success for Convert multiple bind ops to 1 job (rev2)
Date: Wed, 15 May 2024 01:26:26 -0000 [thread overview]
Message-ID: <171573638692.2116540.2402639305677463646@8e613ede5ea5> (raw)
In-Reply-To: <20240515004010.100091-1-matthew.brost@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1269 bytes --]
== Series Details ==
Series: Convert multiple bind ops to 1 job (rev2)
URL : https://patchwork.freedesktop.org/series/133034/
State : success
== Summary ==
CI Bug Log - changes from xe-1286-4cb2d17202b74ed81c0b6f22e540d811458869df_BAT -> xe-pw-133034v2_BAT
====================================================
Summary
-------
**SUCCESS**
No regressions found.
Participating hosts (5 -> 5)
------------------------------
No changes in participating hosts
Known issues
------------
Here are the changes found in xe-pw-133034v2_BAT that come from known issues:
### IGT changes ###
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[Intel XE#886]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/886
Build changes
-------------
* Linux: xe-1286-4cb2d17202b74ed81c0b6f22e540d811458869df -> xe-pw-133034v2
IGT_7854: 8abb25ffe588020cf0b797d60ad1f3f9e7c0764a @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
xe-1286-4cb2d17202b74ed81c0b6f22e540d811458869df: 4cb2d17202b74ed81c0b6f22e540d811458869df
xe-pw-133034v2: 133034v2
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-133034v2/index.html
[-- Attachment #2: Type: text/html, Size: 1748 bytes --]
next prev parent reply other threads:[~2024-05-15 1:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 0:40 [PATCH v2 0/6] Convert multiple bind ops to 1 job Matthew Brost
2024-05-15 0:40 ` [PATCH v2 1/6] drm/xe: s/xe_tile_migrate_engine/xe_tile_migrate_exec_queue Matthew Brost
2024-05-15 20:56 ` Cavitt, Jonathan
2024-05-18 2:42 ` Zeng, Oak
2024-05-15 0:40 ` [PATCH v2 2/6] drm/xe: Add xe_vm_pgtable_update_op to xe_vma_ops Matthew Brost
2024-05-15 21:56 ` Cavitt, Jonathan
2024-05-15 0:40 ` [PATCH v2 3/6] drm/xe: Convert multiple bind ops into single job Matthew Brost
2024-05-15 0:40 ` [PATCH v2 4/6] drm/xe: Update VM trace events Matthew Brost
2024-05-15 20:59 ` Cavitt, Jonathan
2024-05-15 0:40 ` [PATCH v2 5/6] drm/xe: Update PT layer with better error handling Matthew Brost
2024-05-15 0:40 ` [PATCH v2 6/6] drm/xe: Add VM bind IOCTL error injection Matthew Brost
2024-05-15 21:29 ` Cavitt, Jonathan
2024-05-15 22:45 ` Matthew Brost
2024-05-15 0:44 ` ✓ CI.Patch_applied: success for Convert multiple bind ops to 1 job (rev2) Patchwork
2024-05-15 0:44 ` ✗ CI.checkpatch: warning " Patchwork
2024-05-15 0:45 ` ✓ CI.KUnit: success " Patchwork
2024-05-15 0:57 ` ✓ CI.Build: " Patchwork
2024-05-15 0:59 ` ✓ CI.Hooks: " Patchwork
2024-05-15 1:01 ` ✓ CI.checksparse: " Patchwork
2024-05-15 1:26 ` Patchwork [this message]
2024-05-15 2:53 ` ✗ CI.FULL: failure " Patchwork
2024-05-18 2:41 ` [PATCH v2 0/6] Convert multiple bind ops to 1 job Zeng, Oak
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=171573638692.2116540.2402639305677463646@8e613ede5ea5 \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@intel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).