From: Patchwork <patchwork@emeril.freedesktop.org>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.BAT: failure for series starting with [1/4] drm: Protect master->unique with dev->master_mutex (rev2)
Date: Sun, 11 Dec 2016 13:12:32 -0000 [thread overview]
Message-ID: <20161211131232.4551.69798@emeril.freedesktop.org> (raw)
In-Reply-To: <20161210215255.7765-1-daniel.vetter@ffwll.ch>
== Series Details ==
Series: series starting with [1/4] drm: Protect master->unique with dev->master_mutex (rev2)
URL : https://patchwork.freedesktop.org/series/16661/
State : failure
== Summary ==
Series 16661v2 Series without cover letter
https://patchwork.freedesktop.org/api/1.0/series/16661/revisions/2/mbox/
Test kms_busy:
Subgroup basic-flip-default-a:
pass -> FAIL (fi-ivb-3770)
pass -> FAIL (fi-ilk-650)
pass -> FAIL (fi-skl-6260u)
skip -> FAIL (fi-bsw-n3050)
pass -> FAIL (fi-hsw-4770)
pass -> FAIL (fi-skl-6770hq)
pass -> FAIL (fi-snb-2600)
pass -> FAIL (fi-byt-j1900)
pass -> FAIL (fi-skl-6700k)
pass -> FAIL (fi-hsw-4770r)
pass -> FAIL (fi-kbl-7500u)
pass -> FAIL (fi-bxt-t5700)
pass -> FAIL (fi-byt-n2820)
pass -> FAIL (fi-bdw-5557u)
pass -> FAIL (fi-snb-2520m)
pass -> FAIL (fi-ivb-3520m)
pass -> FAIL (fi-skl-6700hq)
Subgroup basic-flip-default-b:
pass -> FAIL (fi-ivb-3770)
pass -> FAIL (fi-ilk-650)
pass -> FAIL (fi-skl-6260u)
skip -> FAIL (fi-bsw-n3050)
pass -> FAIL (fi-hsw-4770)
pass -> FAIL (fi-skl-6770hq)
pass -> FAIL (fi-snb-2600)
pass -> FAIL (fi-byt-j1900)
pass -> FAIL (fi-skl-6700k)
pass -> FAIL (fi-hsw-4770r)
pass -> FAIL (fi-kbl-7500u)
pass -> FAIL (fi-bxt-t5700)
pass -> FAIL (fi-byt-n2820)
pass -> FAIL (fi-bdw-5557u)
pass -> FAIL (fi-snb-2520m)
pass -> FAIL (fi-ivb-3520m)
pass -> FAIL (fi-skl-6700hq)
Subgroup basic-flip-default-c:
pass -> FAIL (fi-ivb-3770)
skip -> FAIL (fi-ilk-650)
pass -> FAIL (fi-skl-6260u)
pass -> FAIL (fi-bsw-n3050)
pass -> FAIL (fi-hsw-4770)
pass -> FAIL (fi-skl-6770hq)
skip -> FAIL (fi-snb-2600)
skip -> FAIL (fi-byt-j1900)
pass -> FAIL (fi-skl-6700k)
pass -> FAIL (fi-hsw-4770r)
pass -> FAIL (fi-kbl-7500u)
pass -> FAIL (fi-bxt-t5700)
skip -> FAIL (fi-byt-n2820)
pass -> FAIL (fi-bdw-5557u)
skip -> FAIL (fi-snb-2520m)
pass -> FAIL (fi-ivb-3520m)
pass -> FAIL (fi-skl-6700hq)
Test kms_cursor_legacy:
Subgroup basic-busy-flip-before-cursor-atomic:
skip -> FAIL (fi-ivb-3770)
skip -> FAIL (fi-ilk-650)
skip -> FAIL (fi-skl-6260u)
skip -> FAIL (fi-bsw-n3050)
skip -> FAIL (fi-hsw-4770)
skip -> FAIL (fi-skl-6770hq)
skip -> FAIL (fi-snb-2600)
skip -> FAIL (fi-byt-j1900)
skip -> FAIL (fi-skl-6700k)
skip -> FAIL (fi-hsw-4770r)
skip -> FAIL (fi-kbl-7500u)
skip -> FAIL (fi-bxt-t5700)
skip -> FAIL (fi-byt-n2820)
skip -> FAIL (fi-bdw-5557u)
skip -> FAIL (fi-snb-2520m)
skip -> FAIL (fi-ivb-3520m)
skip -> FAIL (fi-skl-6700hq)
Subgroup basic-busy-flip-before-cursor-legacy:
pass -> FAIL (fi-ivb-3770)
pass -> FAIL (fi-ilk-650)
pass -> FAIL (fi-skl-6260u)
pass -> FAIL (fi-bsw-n3050)
pass -> FAIL (fi-hsw-4770)
pass -> FAIL (fi-skl-6770hq)
pass -> FAIL (fi-snb-2600)
pass -> FAIL (fi-byt-j1900)
pass -> FAIL (fi-skl-6700k)
pass -> FAIL (fi-hsw-4770r)
pass -> FAIL (fi-kbl-7500u)
pass -> FAIL (fi-bxt-t5700)
pass -> FAIL (fi-byt-n2820)
pass -> FAIL (fi-bdw-5557u)
pass -> FAIL (fi-snb-2520m)
pass -> FAIL (fi-ivb-3520m)
pass -> FAIL (fi-skl-6700hq)
Subgroup basic-busy-flip-before-cursor-varying-size:
pass -> FAIL (fi-ivb-3770)
pass -> FAIL (fi-ilk-650)
pass -> FAIL (fi-skl-6260u)
pass -> FAIL (fi-bsw-n3050)
WARNING: Long output truncated
f6a248e2507f98d7eb1f4fec8cfcbf685a33d289 drm-tip: 2016y-12m-10d-21h-47m-23s UTC integration manifest
c25f986 drm: Simplify GETRESOURCES ioctl
51ba21c drm: Enforce BKL-less ioctls for modern drivers
5acb428 drm: setclientcap doesn't need the drm BKL
8fd08d9 drm: Protect master->unique with dev->master_mutex
== Logs ==
For more details see: https://intel-gfx-ci.01.org/CI/Patchwork_3262/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-12-11 13:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-10 21:52 [PATCH 1/4] drm: Protect master->unique with dev->master_mutex Daniel Vetter
2016-12-10 21:52 ` [PATCH 2/4] drm: setclientcap doesn't need the drm BKL Daniel Vetter
2016-12-12 9:41 ` [Intel-gfx] " Chris Wilson
2016-12-10 21:52 ` [PATCH 3/4] drm: Enforce BKL-less ioctls for modern drivers Daniel Vetter
2016-12-12 9:50 ` [Intel-gfx] " Chris Wilson
2016-12-13 8:39 ` Daniel Vetter
2016-12-10 21:52 ` [PATCH 4/4] drm: Simplify GETRESOURCES ioctl Daniel Vetter
2016-12-10 22:04 ` Chris Wilson
2016-12-11 10:55 ` Daniel Vetter
2016-12-11 12:39 ` [PATCH] " Daniel Vetter
2016-12-11 15:02 ` Chris Wilson
2016-12-11 19:20 ` Daniel Vetter
2016-12-11 19:53 ` Chris Wilson
2016-12-12 9:24 ` Daniel Vetter
2016-12-10 22:52 ` ✗ Fi.CI.BAT: failure for series starting with [1/4] drm: Protect master->unique with dev->master_mutex Patchwork
2016-12-11 13:12 ` Patchwork [this message]
2016-12-11 19:52 ` ✓ Fi.CI.BAT: success for series starting with [1/4] drm: Protect master->unique with dev->master_mutex (rev3) Patchwork
2016-12-12 9:39 ` [PATCH 1/4] drm: Protect master->unique with dev->master_mutex Chris Wilson
2016-12-13 8:40 ` Daniel Vetter
2016-12-12 13:23 ` Emil Velikov
2016-12-13 8:35 ` Daniel Vetter
2016-12-13 9:42 ` Michel Dänzer
2016-12-13 9:46 ` Daniel Vetter
2016-12-13 15:20 ` Emil Velikov
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=20161211131232.4551.69798@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=daniel.vetter@ffwll.ch \
--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).