From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Matthew Auld" <matthew.auld@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/request: fix early tracepoints
Date: Fri, 03 Sep 2021 12:11:28 -0000 [thread overview]
Message-ID: <163067108887.21416.11434008479829177246@emeril.freedesktop.org> (raw)
In-Reply-To: <20210903112405.1794793-1-matthew.auld@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2776 bytes --]
== Series Details ==
Series: drm/i915/request: fix early tracepoints
URL : https://patchwork.freedesktop.org/series/94317/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10549 -> Patchwork_20951
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20951/index.html
Known issues
------------
Here are the changes found in Patchwork_20951 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@amdgpu/amd_basic@cs-gfx:
- fi-rkl-guc: NOTRUN -> [SKIP][1] ([fdo#109315]) +17 similar issues
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20951/fi-rkl-guc/igt@amdgpu/amd_basic@cs-gfx.html
* igt@amdgpu/amd_cs_nop@sync-fork-compute0:
- fi-snb-2600: NOTRUN -> [SKIP][2] ([fdo#109271]) +17 similar issues
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20951/fi-snb-2600/igt@amdgpu/amd_cs_nop@sync-fork-compute0.html
#### Possible fixes ####
* igt@core_hotunplug@unbind-rebind:
- fi-rkl-guc: [DMESG-WARN][3] ([i915#3925]) -> [PASS][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10549/fi-rkl-guc/igt@core_hotunplug@unbind-rebind.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20951/fi-rkl-guc/igt@core_hotunplug@unbind-rebind.html
* igt@i915_selftest@live@hangcheck:
- fi-snb-2600: [INCOMPLETE][5] ([i915#3921]) -> [PASS][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10549/fi-snb-2600/igt@i915_selftest@live@hangcheck.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20951/fi-snb-2600/igt@i915_selftest@live@hangcheck.html
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109315]: https://bugs.freedesktop.org/show_bug.cgi?id=109315
[i915#3921]: https://gitlab.freedesktop.org/drm/intel/issues/3921
[i915#3925]: https://gitlab.freedesktop.org/drm/intel/issues/3925
Participating hosts (46 -> 38)
------------------------------
Missing (8): fi-kbl-soraka bat-adls-5 fi-hsw-4200u bat-dg1-5 fi-bsw-cyan bat-adlp-4 fi-bdw-samus bat-jsl-1
Build changes
-------------
* Linux: CI_DRM_10549 -> Patchwork_20951
CI-20190529: 20190529
CI_DRM_10549: cd8e346a0b56ce66f94a9908c7a068bbee8f1829 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6197: 40888f97a6ad219f4ed48a1830d0ef3c9617d006 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_20951: c82cbcd35cf9beef272fa314c267c0ced70adbc5 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
c82cbcd35cf9 drm/i915/request: fix early tracepoints
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20951/index.html
[-- Attachment #2: Type: text/html, Size: 3466 bytes --]
next prev parent reply other threads:[~2021-09-03 12:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-03 11:24 [PATCH] drm/i915/request: fix early tracepoints Matthew Auld
2021-09-03 11:24 ` [Intel-gfx] " Matthew Auld
2021-09-03 11:42 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2021-09-03 12:11 ` Patchwork [this message]
2021-09-03 13:27 ` [Intel-gfx] ✓ Fi.CI.IGT: success " Patchwork
2021-09-08 17:38 ` [PATCH] " Daniel Vetter
2021-09-08 17:38 ` [Intel-gfx] " Daniel Vetter
2021-09-09 16:16 ` Matthew Auld
2021-09-09 16:16 ` [Intel-gfx] " Matthew Auld
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=163067108887.21416.11434008479829177246@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@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 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.