From: Patchwork <patchwork@emeril.freedesktop.org>
To: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✓ Fi.CI.BAT: success for series starting with [CI,1/2] drm/i915/guc: always use Command Transport Buffers
Date: Thu, 06 Jun 2019 23:41:48 -0000 [thread overview]
Message-ID: <20190606234148.5895.86129@emeril.freedesktop.org> (raw)
In-Reply-To: <20190606224225.14287-1-daniele.ceraolospurio@intel.com>
== Series Details ==
Series: series starting with [CI,1/2] drm/i915/guc: always use Command Transport Buffers
URL : https://patchwork.freedesktop.org/series/61739/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6211 -> Patchwork_13197
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13197/
Known issues
------------
Here are the changes found in Patchwork_13197 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_selftest@live_contexts:
- fi-bdw-gvtdvm: [PASS][1] -> [DMESG-FAIL][2] ([fdo#110235])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6211/fi-bdw-gvtdvm/igt@i915_selftest@live_contexts.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13197/fi-bdw-gvtdvm/igt@i915_selftest@live_contexts.html
#### Possible fixes ####
* igt@gem_exec_reloc@basic-gtt-noreloc:
- fi-icl-u3: [DMESG-WARN][3] ([fdo#107724]) -> [PASS][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6211/fi-icl-u3/igt@gem_exec_reloc@basic-gtt-noreloc.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13197/fi-icl-u3/igt@gem_exec_reloc@basic-gtt-noreloc.html
* igt@kms_frontbuffer_tracking@basic:
- fi-icl-u2: [FAIL][5] ([fdo#103167]) -> [PASS][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6211/fi-icl-u2/igt@kms_frontbuffer_tracking@basic.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13197/fi-icl-u2/igt@kms_frontbuffer_tracking@basic.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#103167]: https://bugs.freedesktop.org/show_bug.cgi?id=103167
[fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713
[fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724
[fdo#108044]: https://bugs.freedesktop.org/show_bug.cgi?id=108044
[fdo#108569]: https://bugs.freedesktop.org/show_bug.cgi?id=108569
[fdo#108744]: https://bugs.freedesktop.org/show_bug.cgi?id=108744
[fdo#110235]: https://bugs.freedesktop.org/show_bug.cgi?id=110235
Participating hosts (54 -> 46)
------------------------------
Missing (8): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-byt-clapper fi-ivb-3770 fi-icl-dsi fi-bdw-samus
Build changes
-------------
* Linux: CI_DRM_6211 -> Patchwork_13197
CI_DRM_6211: 1f1b3034e607fb7676cea89d5cb7134b7526dd96 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5045: de204870261c0ccda668ef8abc8b756b6e679b4a @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_13197: 2819ce018651eff5113b00fbb829ed9cd1e3f3e8 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
2819ce018651 drm/i915/wopcm: update default size for gen11+
43636eec1ebb drm/i915/guc: always use Command Transport Buffers
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13197/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-06-06 23:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 22:42 [CI 1/2] drm/i915/guc: always use Command Transport Buffers Daniele Ceraolo Spurio
2019-06-06 22:42 ` [CI 2/2] drm/i915/wopcm: update default size for gen11+ Daniele Ceraolo Spurio
2019-06-07 14:46 ` Summers, Stuart
2019-06-06 23:41 ` Patchwork [this message]
2019-06-09 7:10 ` ✓ Fi.CI.IGT: success for series starting with [CI,1/2] drm/i915/guc: always use Command Transport Buffers 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=20190606234148.5895.86129@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=daniele.ceraolospurio@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox