From: Patchwork <patchwork@emeril.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✓ Fi.CI.IGT: success for drm: Differentiate the lack of an interface from invalid parameter (rev4)
Date: Thu, 13 Sep 2018 21:37:40 -0000 [thread overview]
Message-ID: <20180913213740.995.10877@emeril.freedesktop.org> (raw)
In-Reply-To: <20180912082713.23294-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: drm: Differentiate the lack of an interface from invalid parameter (rev4)
URL : https://patchwork.freedesktop.org/series/49536/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4818_full -> Patchwork_10175_full =
== Summary - SUCCESS ==
No regressions found.
== Known issues ==
Here are the changes found in Patchwork_10175_full that come from known issues:
=== IGT changes ===
==== Issues hit ====
igt@kms_setmode@basic:
shard-kbl: PASS -> FAIL (fdo#99912)
==== Possible fixes ====
igt@gem_exec_await@wide-contexts:
shard-kbl: FAIL (fdo#106680) -> PASS
igt@kms_color@pipe-b-ctm-blue-to-red:
shard-apl: DMESG-WARN (fdo#105602, fdo#103558) -> PASS +20
igt@kms_cursor_crc@cursor-128x128-suspend:
shard-snb: DMESG-WARN (fdo#102365) -> PASS
fdo#102365 https://bugs.freedesktop.org/show_bug.cgi?id=102365
fdo#103558 https://bugs.freedesktop.org/show_bug.cgi?id=103558
fdo#105602 https://bugs.freedesktop.org/show_bug.cgi?id=105602
fdo#106680 https://bugs.freedesktop.org/show_bug.cgi?id=106680
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_4818 -> Patchwork_10175
CI_DRM_4818: da3d33f1d75f54cf29f08dba582694792980cd9b @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4640: 9a8da36e708f9ed15b20689dfe305e41f9a19008 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_10175: e4b70966e99a538f3460e1e6640d6f5389c1aa2d @ 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_10175/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-13 21:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 8:27 [PATCH] drm: Differentiate the lack of an interface from invalid parameter Chris Wilson
2018-09-12 8:39 ` Daniel Vetter
2018-09-12 8:50 ` Chris Wilson
2018-09-12 9:02 ` Daniel Vetter
2018-09-12 9:12 ` Chris Wilson
2018-09-12 16:26 ` Christian König
2018-09-12 8:58 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-09-12 9:26 ` [PATCH v2] " Chris Wilson
2018-09-12 9:29 ` [PATCH v3] " Chris Wilson
2018-09-13 13:30 ` Daniel Vetter
2018-09-13 19:20 ` Chris Wilson
2018-09-14 16:58 ` Chris Wilson
2018-09-12 9:58 ` ✓ Fi.CI.BAT: success for drm: Differentiate the lack of an interface from invalid parameter (rev3) Patchwork
2018-09-12 12:23 ` ✓ Fi.CI.IGT: " Patchwork
2018-09-13 19:50 ` ✓ Fi.CI.BAT: success for drm: Differentiate the lack of an interface from invalid parameter (rev4) Patchwork
2018-09-13 21:37 ` 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=20180913213740.995.10877@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=chris@chris-wilson.co.uk \
--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