From: Patchwork <patchwork@emeril.freedesktop.org>
To: Karthik B S <karthik.b.s@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✓ Fi.CI.IGT: success for series starting with [v2,1/2] drm/i915/icl: Avoid Gen10 watermark workarounds in Gen11 (rev2)
Date: Fri, 07 Sep 2018 07:18:56 -0000 [thread overview]
Message-ID: <20180907071856.6599.30426@emeril.freedesktop.org> (raw)
In-Reply-To: <1536138159-10842-1-git-send-email-karthik.b.s@intel.com>
== Series Details ==
Series: series starting with [v2,1/2] drm/i915/icl: Avoid Gen10 watermark workarounds in Gen11 (rev2)
URL : https://patchwork.freedesktop.org/series/49170/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4785_full -> Patchwork_10119_full =
== Summary - SUCCESS ==
No regressions found.
== Known issues ==
Here are the changes found in Patchwork_10119_full that come from known issues:
=== IGT changes ===
==== Issues hit ====
igt@gem_workarounds@suspend-resume-context:
shard-kbl: PASS -> INCOMPLETE (fdo#103665)
igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-shrfb-pgflip-blt:
shard-glk: PASS -> FAIL (fdo#103167)
==== Possible fixes ====
igt@kms_setmode@basic:
shard-apl: FAIL (fdo#99912) -> PASS
shard-kbl: FAIL (fdo#99912) -> PASS
igt@perf@polling:
shard-hsw: FAIL (fdo#102252) -> PASS
fdo#102252 https://bugs.freedesktop.org/show_bug.cgi?id=102252
fdo#103167 https://bugs.freedesktop.org/show_bug.cgi?id=103167
fdo#103665 https://bugs.freedesktop.org/show_bug.cgi?id=103665
fdo#99912 https://bugs.freedesktop.org/show_bug.cgi?id=99912
== Participating hosts (5 -> 5) ==
No changes in participating hosts
== Build changes ==
* Linux: CI_DRM_4785 -> Patchwork_10119
CI_DRM_4785: 7fddb79b0908d5c08efc93656fd10a761c9d14ca @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4634: 7d89cc39dde3b4881d85ace45d504cc098fa3684 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_10119: 09a385355f4266d08f71994130cef2598d4ab027 @ git://anongit.freedesktop.org/gfx-ci/linux
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_10119/shards.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2018-09-07 7:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 9:02 [PATCH v2 1/2] drm/i915/icl: Avoid Gen10 watermark workarounds in Gen11 Karthik B S
2018-09-05 9:02 ` [PATCH v2 2/2] drm/i915/icl: Update result lines in correspondence with result blocks Karthik B S
2018-09-05 23:42 ` Rodrigo Vivi
2018-09-06 9:39 ` B S, Karthik
2018-09-06 10:27 ` [PATCH v3 2/2] drm/i915/skl+: " Karthik B S
2018-09-05 9:47 ` ✓ Fi.CI.BAT: success for series starting with [v2,1/2] drm/i915/icl: Avoid Gen10 watermark workarounds in Gen11 Patchwork
2018-09-05 10:38 ` ✓ Fi.CI.IGT: " Patchwork
2018-09-05 23:41 ` [PATCH v2 1/2] " Rodrigo Vivi
2018-10-11 17:45 ` Paulo Zanoni
2018-09-06 13:35 ` ✓ Fi.CI.BAT: success for series starting with [v2,1/2] drm/i915/icl: Avoid Gen10 watermark workarounds in Gen11 (rev2) Patchwork
2018-09-06 15:00 ` ✗ Fi.CI.IGT: failure " Patchwork
2018-09-07 5:25 ` ✓ Fi.CI.BAT: success " Patchwork
2018-09-07 7:18 ` Patchwork [this message]
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=20180907071856.6599.30426@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=karthik.b.s@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox