From: Patchwork <patchwork@emeril.freedesktop.org>
To: Paulo Zanoni <paulo.r.zanoni@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✓ Fi.CI.BAT: success for drm/i915/icl: implement the tc/legacy HPD {dis, }connect flows (rev2)
Date: Thu, 23 Aug 2018 22:17:23 -0000 [thread overview]
Message-ID: <20180823221723.8838.73989@emeril.freedesktop.org> (raw)
In-Reply-To: <20180731234504.5553-1-paulo.r.zanoni@intel.com>
== Series Details ==
Series: drm/i915/icl: implement the tc/legacy HPD {dis, }connect flows (rev2)
URL : https://patchwork.freedesktop.org/series/47518/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4702 -> Patchwork_10002 =
== Summary - SUCCESS ==
No regressions found.
External URL: https://patchwork.freedesktop.org/api/1.0/series/47518/revisions/2/mbox/
== Possible new issues ==
Here are the unknown changes that may have been introduced in Patchwork_10002:
=== IGT changes ===
==== Warnings ====
{igt@pm_rpm@module-reload}:
fi-byt-n2820: DMESG-FAIL -> DMESG-WARN
== Known issues ==
Here are the changes found in Patchwork_10002 that come from known issues:
=== IGT changes ===
==== Issues hit ====
igt@debugfs_test@read_all_entries:
fi-kbl-r: PASS -> DMESG-WARN (fdo#105602)
igt@kms_frontbuffer_tracking@basic:
{fi-byt-clapper}: PASS -> FAIL (fdo#103167)
igt@kms_pipe_crc_basic@nonblocking-crc-pipe-b:
{fi-byt-clapper}: PASS -> FAIL (fdo#107362)
{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#105602 https://bugs.freedesktop.org/show_bug.cgi?id=105602
fdo#107362 https://bugs.freedesktop.org/show_bug.cgi?id=107362
== Participating hosts (53 -> 48) ==
Missing (5): fi-ctg-p8600 fi-ilk-m540 fi-byt-squawks fi-bsw-cyan fi-hsw-4200u
== Build changes ==
* Linux: CI_DRM_4702 -> Patchwork_10002
CI_DRM_4702: 0349bfb08204a6b44f16551c2be3b58563ff73d2 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4608: 94ebd21177feedf03e8f6dd1e73dca1a6ec7a0ac @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_10002: 2b4ca525e11918638986e975d28f7f5a5e8b4de2 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
2b4ca525e119 drm/i915/icl: implement the tc/legacy HPD {dis, }connect flows
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_10002/issues.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-23 22:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 23:45 [PATCH] drm/i915/icl: implement the tc/legacy HPD {dis, }connect flows Paulo Zanoni
2018-08-01 0:21 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-08-01 1:15 ` ✓ Fi.CI.IGT: " Patchwork
2018-08-01 8:22 ` [PATCH] " Chris Wilson
2018-08-01 17:05 ` Paulo Zanoni
2018-08-01 17:34 ` [PATCH v3] " Paulo Zanoni
2018-08-17 16:25 ` Srivatsa, Anusha
2018-08-17 23:27 ` Paulo Zanoni
2018-08-23 1:07 ` Rodrigo Vivi
2018-08-01 18:34 ` ✗ Fi.CI.BAT: failure for drm/i915/icl: implement the tc/legacy HPD {dis, }connect flows (rev2) Patchwork
2018-08-23 22:17 ` Patchwork [this message]
2018-08-23 23:30 ` ✗ 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=20180823221723.8838.73989@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=paulo.r.zanoni@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;
as well as URLs for NNTP newsgroup(s).