From: Patchwork <patchwork@emeril.freedesktop.org>
To: "HardikX Deepakkumar patel" <hardikx.deepakkumar.patel@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/selftests: Memory mapping with IOMMU
Date: Tue, 11 May 2021 06:37:37 -0000 [thread overview]
Message-ID: <162071505723.32035.1765128612696474590@emeril.freedesktop.org> (raw)
In-Reply-To: <20210511054239.214607-1-hardikx.deepakkumar.patel@intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 2900 bytes --]
== Series Details ==
Series: drm/i915/selftests: Memory mapping with IOMMU
URL : https://patchwork.freedesktop.org/series/89987/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10064 -> Patchwork_20096
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20096/index.html
Known issues
------------
Here are the changes found in Patchwork_20096 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_selftest@live@execlists:
- fi-cfl-8109u: [PASS][1] -> [DMESG-WARN][2] ([i915#203]) +3 similar issues
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10064/fi-cfl-8109u/igt@i915_selftest@live@execlists.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20096/fi-cfl-8109u/igt@i915_selftest@live@execlists.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#109285]: https://bugs.freedesktop.org/show_bug.cgi?id=109285
[fdo#109315]: https://bugs.freedesktop.org/show_bug.cgi?id=109315
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1072]: https://gitlab.freedesktop.org/drm/intel/issues/1072
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#203]: https://gitlab.freedesktop.org/drm/intel/issues/203
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#2411]: https://gitlab.freedesktop.org/drm/intel/issues/2411
[i915#3012]: https://gitlab.freedesktop.org/drm/intel/issues/3012
[i915#3276]: https://gitlab.freedesktop.org/drm/intel/issues/3276
[i915#3277]: https://gitlab.freedesktop.org/drm/intel/issues/3277
[i915#3282]: https://gitlab.freedesktop.org/drm/intel/issues/3282
[i915#3283]: https://gitlab.freedesktop.org/drm/intel/issues/3283
[i915#3291]: https://gitlab.freedesktop.org/drm/intel/issues/3291
[i915#3301]: https://gitlab.freedesktop.org/drm/intel/issues/3301
[i915#533]: https://gitlab.freedesktop.org/drm/intel/issues/533
Participating hosts (40 -> 39)
------------------------------
Additional (1): fi-rkl-11500t
Missing (2): fi-ilk-m540 fi-bdw-samus
Build changes
-------------
* Linux: CI_DRM_10064 -> Patchwork_20096
CI-20190529: 20190529
CI_DRM_10064: eb2730cd1643ffb717211862c1d66eeb8e5b31cf @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6081: fdff4bba7abf9cb7c8ea21abf14e36d344ebb8c1 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_20096: d70eeba8b0773f534bcda0a998dbc3f4efef8bc9 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
d70eeba8b077 drm/i915/selftests: Memory mapping with IOMMU
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20096/index.html
[-- Attachment #1.2: Type: text/html, Size: 2491 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2021-05-11 6:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 5:42 [Intel-gfx] [PATCH] drm/i915/selftests: Memory mapping with IOMMU HardikX Deepakkumar patel
2021-05-11 6:37 ` Patchwork [this message]
2021-05-11 8:26 ` [Intel-gfx] ✓ Fi.CI.IGT: success 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=162071505723.32035.1765128612696474590@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=hardikx.deepakkumar.patel@intel.com \
--cc=intel-gfx@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 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.