From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Nilawar, Badal" <badal.nilawar@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: ✓ CI.BAT: success for Workaround to handle G2H timeout (rev2)
Date: Fri, 18 Oct 2024 03:49:21 -0000 [thread overview]
Message-ID: <172922336167.1280853.4519834012548434030@2413ebb6fbb6> (raw)
In-Reply-To: <20241017111410.2553784-1-badal.nilawar@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1656 bytes --]
== Series Details ==
Series: Workaround to handle G2H timeout (rev2)
URL : https://patchwork.freedesktop.org/series/140056/
State : success
== Summary ==
CI Bug Log - changes from xe-2075-81420006f741f9783adea6ab5620ce54697f1b20_BAT -> xe-pw-140056v2_BAT
====================================================
Summary
-------
**SUCCESS**
No regressions found.
Participating hosts (9 -> 9)
------------------------------
No changes in participating hosts
Known issues
------------
Here are the changes found in xe-pw-140056v2_BAT that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@kms_frontbuffer_tracking@basic:
- bat-adlp-7: [PASS][1] -> [FAIL][2] ([Intel XE#1861])
[1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2075-81420006f741f9783adea6ab5620ce54697f1b20/bat-adlp-7/igt@kms_frontbuffer_tracking@basic.html
[2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-140056v2/bat-adlp-7/igt@kms_frontbuffer_tracking@basic.html
[Intel XE#1861]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1861
Build changes
-------------
* IGT: IGT_8077 -> IGT_8078
* Linux: xe-2075-81420006f741f9783adea6ab5620ce54697f1b20 -> xe-pw-140056v2
IGT_8077: 42f9e9702f74a4993318adea936baaa186084689 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
IGT_8078: 175bddf20141ccad40130719ca46bde5140f4872 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
xe-2075-81420006f741f9783adea6ab5620ce54697f1b20: 81420006f741f9783adea6ab5620ce54697f1b20
xe-pw-140056v2: 140056v2
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-140056v2/index.html
[-- Attachment #2: Type: text/html, Size: 2235 bytes --]
prev parent reply other threads:[~2024-10-18 3:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 11:14 [PATCH v3 0/1] Workaround to handle G2H timeout Badal Nilawar
2024-10-17 11:14 ` [PATCH v3 1/1] drm/xe/guc/ct: Flush g2h worker in case of g2h response timeout Badal Nilawar
2024-10-17 13:43 ` Ghimiray, Himal Prasad
2024-10-17 15:17 ` Matthew Brost
2024-10-18 0:05 ` John Harrison
2024-10-17 11:15 ` ✓ CI.Patch_applied: success for Workaround to handle G2H timeout (rev2) Patchwork
2024-10-17 11:15 ` ✓ CI.checkpatch: " Patchwork
2024-10-17 11:16 ` ✓ CI.KUnit: " Patchwork
2024-10-17 11:28 ` ✓ CI.Build: " Patchwork
2024-10-17 11:30 ` ✓ CI.Hooks: " Patchwork
2024-10-17 11:32 ` ✓ CI.checksparse: " Patchwork
2024-10-17 22:36 ` ✗ CI.FULL: failure " Patchwork
2024-10-18 3:49 ` Patchwork [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=172922336167.1280853.4519834012548434030@2413ebb6fbb6 \
--to=patchwork@emeril.freedesktop.org \
--cc=badal.nilawar@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