From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Jesse Zhang" <jesse.zhang@amd.com>
Cc: igt-dev@lists.freedesktop.org
Subject: [igt-dev] ✓ Fi.CI.BAT: success for tests/amdgpu: fix secure bounce test issue
Date: Wed, 29 Nov 2023 08:55:41 -0000 [thread overview]
Message-ID: <170124814107.12090.11958396400681460257@emeril.freedesktop.org> (raw)
In-Reply-To: <20231129080307.135383-1-jesse.zhang@amd.com>
[-- Attachment #1: Type: text/plain, Size: 2482 bytes --]
== Series Details ==
Series: tests/amdgpu: fix secure bounce test issue
URL : https://patchwork.freedesktop.org/series/127022/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13943 -> IGTPW_10287
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_10287/index.html
Participating hosts (39 -> 37)
------------------------------
Missing (2): bat-dg2-9 fi-snb-2520m
Known issues
------------
Here are the changes found in IGTPW_10287 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@kms_force_connector_basic@force-connector-state:
- bat-rpls-1: [PASS][1] -> [ABORT][2] ([i915#9315])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13943/bat-rpls-1/igt@kms_force_connector_basic@force-connector-state.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_10287/bat-rpls-1/igt@kms_force_connector_basic@force-connector-state.html
* igt@kms_hdmi_inject@inject-audio:
- fi-kbl-guc: [PASS][3] -> [FAIL][4] ([IGT#3])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13943/fi-kbl-guc/igt@kms_hdmi_inject@inject-audio.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_10287/fi-kbl-guc/igt@kms_hdmi_inject@inject-audio.html
* igt@kms_pipe_crc_basic@read-crc-frame-sequence@pipe-d-edp-1:
- bat-rplp-1: [PASS][5] -> [ABORT][6] ([i915#8668])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13943/bat-rplp-1/igt@kms_pipe_crc_basic@read-crc-frame-sequence@pipe-d-edp-1.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_10287/bat-rplp-1/igt@kms_pipe_crc_basic@read-crc-frame-sequence@pipe-d-edp-1.html
[IGT#3]: https://gitlab.freedesktop.org/drm/igt-gpu-tools/issues/3
[i915#8668]: https://gitlab.freedesktop.org/drm/intel/issues/8668
[i915#9315]: https://gitlab.freedesktop.org/drm/intel/issues/9315
Build changes
-------------
* CI: CI-20190529 -> None
* IGT: IGT_7609 -> IGTPW_10287
CI-20190529: 20190529
CI_DRM_13943: 0417ec152200d74916f157bfe76677b3b4af8224 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_10287: 10287
IGT_7609: 72a759595100b8d167ca78cd2d62e9acd97e36bf @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Testlist changes
----------------
+++ 63 lines
--- 139 lines
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_10287/index.html
[-- Attachment #2: Type: text/html, Size: 3142 bytes --]
next prev parent reply other threads:[~2023-11-29 8:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 8:03 [igt-dev] [PATCH i-g-t] tests/amdgpu: fix secure bounce test issue Jesse Zhang
2023-11-29 8:53 ` [igt-dev] ✓ CI.xeBAT: success for " Patchwork
2023-11-29 8:55 ` Patchwork [this message]
2023-11-29 20:15 ` [igt-dev] [PATCH i-g-t] " vitaly prosyak
2023-11-30 1:09 ` Zhang, Jesse(Jie)
2023-11-30 3:16 ` [igt-dev] ✗ Fi.CI.IGT: failure for " 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=170124814107.12090.11958396400681460257@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=igt-dev@lists.freedesktop.org \
--cc=jesse.zhang@amd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.