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
Date: Wed, 05 Sep 2018 10:38:18 -0000 [thread overview]
Message-ID: <20180905103818.5305.9962@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
URL : https://patchwork.freedesktop.org/series/49170/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4770_full -> Patchwork_10089_full =
== Summary - SUCCESS ==
No regressions found.
== Known issues ==
Here are the changes found in Patchwork_10089_full that come from known issues:
=== IGT changes ===
==== Issues hit ====
igt@kms_setmode@basic:
shard-kbl: PASS -> FAIL (fdo#99912)
==== Possible fixes ====
igt@drv_suspend@shrink:
shard-snb: FAIL (fdo#106886) -> PASS
igt@kms_busy@extended-modeset-hang-newfb-render-b:
shard-glk: INCOMPLETE (fdo#103359, k.org#198133) -> PASS
igt@kms_flip@flip-vs-expired-vblank:
shard-glk: FAIL (fdo#105363) -> PASS
fdo#103359 https://bugs.freedesktop.org/show_bug.cgi?id=103359
fdo#105363 https://bugs.freedesktop.org/show_bug.cgi?id=105363
fdo#106886 https://bugs.freedesktop.org/show_bug.cgi?id=106886
fdo#99912 https://bugs.freedesktop.org/show_bug.cgi?id=99912
k.org#198133 https://bugzilla.kernel.org/show_bug.cgi?id=198133
== Participating hosts (5 -> 5) ==
No changes in participating hosts
== Build changes ==
* Linux: CI_DRM_4770 -> Patchwork_10089
CI_DRM_4770: 0c3535cf60140d017a5df73d84d06e8b1a5b5d3b @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4627: e0c3033a57d85c0d2eb33af0451afa16edc79f10 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_10089: cc78792e068cbd9eca8d10c2f96c724b3e89a957 @ 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_10089/shards.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-09-05 10:38 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 ` Patchwork [this message]
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 ` ✓ Fi.CI.IGT: " 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=20180905103818.5305.9962@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