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 series starting with [v5,1/8] drm/i915: make local-memory probing a GT operation (rev2)
Date: Thu, 28 Jan 2021 14:22:31 -0000 [thread overview]
Message-ID: <161184375105.13615.151687945289937418@emeril.freedesktop.org> (raw)
In-Reply-To: <20210127131417.393872-1-matthew.auld@intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 3162 bytes --]
== Series Details ==
Series: series starting with [v5,1/8] drm/i915: make local-memory probing a GT operation (rev2)
URL : https://patchwork.freedesktop.org/series/86355/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9693 -> Patchwork_19527
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19527/index.html
Known issues
------------
Here are the changes found in Patchwork_19527 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@amdgpu/amd_cs_nop@sync-gfx0:
- fi-bsw-n3050: NOTRUN -> [SKIP][1] ([fdo#109271]) +17 similar issues
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19527/fi-bsw-n3050/igt@amdgpu/amd_cs_nop@sync-gfx0.html
* igt@prime_vgem@basic-fence-flip:
- fi-tgl-y: [PASS][2] -> [DMESG-WARN][3] ([i915#402]) +1 similar issue
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9693/fi-tgl-y/igt@prime_vgem@basic-fence-flip.html
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19527/fi-tgl-y/igt@prime_vgem@basic-fence-flip.html
#### Possible fixes ####
* igt@fbdev@write:
- fi-tgl-y: [DMESG-WARN][4] ([i915#402]) -> [PASS][5] +2 similar issues
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9693/fi-tgl-y/igt@fbdev@write.html
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19527/fi-tgl-y/igt@fbdev@write.html
* igt@i915_selftest@live@execlists:
- fi-bsw-n3050: [INCOMPLETE][6] ([i915#2940]) -> [PASS][7]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9693/fi-bsw-n3050/igt@i915_selftest@live@execlists.html
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19527/fi-bsw-n3050/igt@i915_selftest@live@execlists.html
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[i915#2940]: https://gitlab.freedesktop.org/drm/intel/issues/2940
[i915#402]: https://gitlab.freedesktop.org/drm/intel/issues/402
Participating hosts (44 -> 38)
------------------------------
Missing (6): fi-jsl-1 fi-ilk-m540 fi-hsw-4200u fi-bsw-cyan fi-bsw-kefka fi-bdw-samus
Build changes
-------------
* Linux: CI_DRM_9693 -> Patchwork_19527
CI-20190529: 20190529
CI_DRM_9693: 0a2c27ba1783f0990c2c448c105682e7885120a1 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5976: 1d3b7bde430dd7ea946682d1df46a483b6a93272 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_19527: a77633bc8ce12e87c74c3238abaccc646fff437d @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
a77633bc8ce1 drm/i915: allocate cmd ring in lmem
054586a67eb0 drm/i915: move engine scratch to LMEM
717bbf43447c drm/i915: allocate context from LMEM
878040dcab1f drm/i915/dg1: Reserve first 1MB of local memory
fa4053331dd1 drm/i915: introduce mem->reserved
555325d53cd8 drm/i915: reserve stolen for LMEM region
4b38ca0a0740 drm/i915: setup the LMEM region
9bdaab539cc2 drm/i915: make local-memory probing a GT operation
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19527/index.html
[-- Attachment #1.2: Type: text/html, Size: 3967 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-01-28 14:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 13:14 [Intel-gfx] [PATCH v5 1/8] drm/i915: make local-memory probing a GT operation Matthew Auld
2021-01-27 13:14 ` [Intel-gfx] [PATCH v5 2/8] drm/i915: setup the LMEM region Matthew Auld
2021-01-27 13:14 ` [Intel-gfx] [PATCH v5 3/8] drm/i915: reserve stolen for " Matthew Auld
2021-01-27 13:14 ` [Intel-gfx] [PATCH v5 4/8] drm/i915: introduce mem->reserved Matthew Auld
2021-01-27 13:14 ` [Intel-gfx] [PATCH v5 5/8] drm/i915/dg1: Reserve first 1MB of local memory Matthew Auld
2021-01-27 13:14 ` [Intel-gfx] [PATCH v5 6/8] drm/i915: allocate context from LMEM Matthew Auld
2021-01-27 13:14 ` [Intel-gfx] [PATCH v5 7/8] drm/i915: move engine scratch to LMEM Matthew Auld
2021-01-27 13:14 ` [Intel-gfx] [PATCH v5 8/8] drm/i915: allocate cmd ring in lmem Matthew Auld
2021-01-27 17:21 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [v5,1/8] drm/i915: make local-memory probing a GT operation Patchwork
2021-01-27 17:23 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-01-27 17:50 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2021-01-28 13:53 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [v5,1/8] drm/i915: make local-memory probing a GT operation (rev2) Patchwork
2021-01-28 13:54 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-01-28 14:22 ` Patchwork [this message]
2021-01-29 3:42 ` [Intel-gfx] ✓ Fi.CI.IGT: success " 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=161184375105.13615.151687945289937418@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.