From: Patchwork <patchwork@emeril.freedesktop.org>
To: Jan-Marek Glogowski <glogow@fbihome.de>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✓ Fi.CI.IGT: success for drm/i915: Re-apply "Perform link quality check, unconditionally during long pulse" (rev2)
Date: Mon, 06 Aug 2018 19:27:55 -0000 [thread overview]
Message-ID: <20180806192755.4305.60794@emeril.freedesktop.org> (raw)
In-Reply-To: <01e90c34-a95e-73ba-f9af-c6f3310c4f4d@fbihome.de>
== Series Details ==
Series: drm/i915: Re-apply "Perform link quality check, unconditionally during long pulse" (rev2)
URL : https://patchwork.freedesktop.org/series/47694/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4621_full -> Patchwork_9861_full =
== Summary - WARNING ==
Minor unknown changes coming with Patchwork_9861_full need to be verified
manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_9861_full, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
== Possible new issues ==
Here are the unknown changes that may have been introduced in Patchwork_9861_full:
=== IGT changes ===
==== Warnings ====
igt@pm_rc6_residency@rc6-accuracy:
shard-kbl: SKIP -> PASS
shard-snb: SKIP -> PASS
== Known issues ==
Here are the changes found in Patchwork_9861_full that come from known issues:
=== IGT changes ===
==== Issues hit ====
igt@gem_exec_parallel@fds:
shard-snb: PASS -> INCOMPLETE (fdo#105411)
igt@kms_setmode@basic:
shard-hsw: PASS -> FAIL (fdo#99912)
==== Possible fixes ====
igt@drv_selftest@live_workarounds:
shard-kbl: DMESG-FAIL (fdo#107292) -> PASS
igt@gem_eio@reset-stress:
shard-hsw: FAIL (fdo#107500) -> PASS
igt@kms_flip@2x-flip-vs-expired-vblank:
shard-glk: FAIL (fdo#105363) -> PASS
igt@kms_setmode@basic:
shard-apl: FAIL (fdo#99912) -> PASS
fdo#105363 https://bugs.freedesktop.org/show_bug.cgi?id=105363
fdo#105411 https://bugs.freedesktop.org/show_bug.cgi?id=105411
fdo#107292 https://bugs.freedesktop.org/show_bug.cgi?id=107292
fdo#107500 https://bugs.freedesktop.org/show_bug.cgi?id=107500
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_4621 -> Patchwork_9861
CI_DRM_4621: b35c6b4ccdc1e9b386d5679282123099cf83adf1 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4587: 5d78c73d871525ec9caecd88ad7d9abe36637314 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_9861: 6e96f6b9a9cb0e8d4a3826b549272716d806841f @ 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_9861/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-08-06 19:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-03 18:10 [PATCH] drm/i915: Re-apply "Perform link quality check, unconditionally during long pulse" Jan-Marek Glogowski
2018-08-04 1:36 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2018-08-06 10:25 ` [PATCH] v2 " Jan-Marek Glogowski
2018-08-07 19:33 ` Lyude Paul
2018-08-07 22:26 ` Jan-Marek Glogowski
2018-08-07 22:46 ` Lyude Paul
2018-08-08 8:53 ` [PATCH] v3 " Jan-Marek Glogowski
2018-08-13 16:35 ` Lyude Paul
2018-08-16 18:03 ` Manasi Navare
2018-08-16 19:12 ` Jan-Marek Glogowski
2018-08-17 11:12 ` Jan-Marek Glogowski
2018-08-17 20:33 ` Lyude Paul
2018-08-04 1:53 ` ✗ Fi.CI.BAT: failure for " Patchwork
2018-08-06 16:34 ` ✓ Fi.CI.BAT: success for drm/i915: Re-apply "Perform link quality check, unconditionally during long pulse" (rev2) Patchwork
2018-08-06 19:27 ` Patchwork [this message]
2018-08-08 23:17 ` ✓ Fi.CI.BAT: success for drm/i915: Re-apply "Perform link quality check, unconditionally during long pulse" (rev3) Patchwork
2018-08-09 2:39 ` ✓ 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=20180806192755.4305.60794@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=glogow@fbihome.de \
--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;
as well as URLs for NNTP newsgroup(s).